Purge Notification Data

POST 
/v1/notifications/:notificationId/purge

This endpoint is used to purge the data of a specific notification. This is used in case of downstream services requiring data deletion after processing - namely for compliance and privacy reasons.

Request

Responses

200

Notification purged successfully

401

Missing or invalid authentication token (GEN001002) or Role unauthorized (GEN001006) or Tenant context could not be resolved (AUT001001)

403

External application access denied (AUT003001) or Party not in required status (PAR003001)

404

Party not found (PAR004001) or No open binding for the notification (CRT004005) or Notification not found (GEN004001)

500

General internal server error (GEN100000) or Service error (GEN100001)

503

All connector targets are currently unhealthy (CRT103001)