Delete the caller's subscriber profile

POST 
/api/v1/notifications/manage/delete-subscriber

Requests deletion of the authenticated beneficiary's subscriber at the configured provider. An absent subscriber is an idempotent success.

Inspect nested status.acknowledged. A missing status is unknown: the current handler can return an empty HTTP 200 response on configuration, network or provider errors. Reconcile that outcome instead of declaring cleanup complete. Provider acknowledgment does not certify complete erasure of queued work, remote copies or platform records.

The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized scoped domain action.

Use this in a guide: Welcome a new user with an in-app message

Request

Responses

200

Provider acknowledgment when present; HTTP success alone does not confirm deletion.

Delete the subscriber selected by authentication; no subscriber ID is accepted in this body.

Section ID: DOC-CP-notifications-api-deleteSubscriber#example-notifications-deleteSubscriber-request

Request example

{}

Illustrative response shape; omitted default fields and actual outcomes depend on the operation.

Section ID: DOC-CP-notifications-api-deleteSubscriber#example-notifications-deleteSubscriber-response

Response example

{
  "status": {
    "acknowledged": true,
    "status": "example"
  }
}

Document ID: DOC-CP-notifications-api-deleteSubscriber. Section identities and revisions.

Section	Stable reference
Delete the caller's subscriber profile	DOC-CP-notifications-api-deleteSubscriber#overview
Request	DOC-CP-notifications-api-deleteSubscriber#request
Responses	DOC-CP-notifications-api-deleteSubscriber#responses