---
title: "Notify Digital Card Operation"
method: POST
path: "/issuers/{issuerId}/digitalCards/{digitalCardId}/notifications"
---

# Notify Digital Card Operation

`POST /issuers/{issuerId}/digitalCards/{digitalCardId}/notifications`

This request is used by D1 to notify the issuer's backend about all operations done on a digital card.

## Request body

- object — The following objects represent the notify digital card request body
  - `operationId` string — Unique identifier of the operation
  - `operation` 'SUSPEND' | 'DELETE' | 'RESUME' | 'RENEW' | 'UPDATE' | 'DELETE_FROM_APP' — The lifecycle operation name performed on the target digital card.<br/> A digital card can be activated(i.e. resumed), suspended, deleted from the wallet application or CCI portal; it can also be renewed when expired by the TSP and updated after a card update/renewal operation (concerning a PAN and/or expiry date update).
  - `status` 'SUCCESSFUL' | 'FAILED' — Status of the operation

## Response `204`

Successful

## Other responses

- `400` — Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
- `401` — The provided Authorization header is missing or invalid
- `404` — Resource not found. Unknown issuerId or consumerId or accountId or cardId
- `500` — Internal Server Error

---

[API](https://skmtc.net/thalescloud/apis/d1-oauth-api.md) · [All operations](https://skmtc.net/thalescloud/apis/d1-oauth-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/thalescloud/d1-oauth-api/versions/96089514858c/schema)