Skip to main content

Delete Customer (GDPR)

Anonymises the Azotte projection of the customer. The record is not physically deleted — it is rewritten so all PII fields become GDPR-compliant placeholders while non-PII operational data (subscription IDs, payment history references, analytics keys) is preserved.

URL

POST /api/c2a/customer/delete

Request Parameters

Body: DeleteCustomerRequest.

NameTypeDescription
customerUuidstringRequired. The Azotte CustomerUrn to anonymise.

Request Example

{ "customerUuid": "cu.00.482" }

Response Parameters

DeleteCustomerResponse.

NameTypeDescription
statusobject (AzotteStatus)Operation status envelope.
status.messageCodestringSUCCESS on hit.

Sample Response

{ "status": { "messageCode": "SUCCESS" } }

Behaviour

  • Idempotent: calling delete on an already-anonymised record returns SUCCESS and changes nothing.
  • Open subscriptions are not canceled by this call — cancel them via the Subscription API first if you also want billing to stop.
  • Historical / analytical aggregations remain queryable via the customer key.

Sample Codes

curl --location 'https://acme.sandbox.azotte.com/api/v1/c2a/customer/delete' \
--header 'Content-Type: application/json' \
--header 'x-tn: e2a1c7b2-4f3a-4b8e-9c2d-1a2b3c4d5e6f' \
--header 'x-api-key: sk_dev_acme_sample_123456789' \
--data '{ "customerUuid": "cu.00.482" }'