Erase subject data
Article 17 erasure, in whichever of the two forms the tenant chooses.
deletehttps://api.integrable.cloud/api/agents/{agent_id}/contacts/{contact_id}/data
- Authentication
- Bearer token
- Retries
- Idempotency-Key
- Body
- None
- Version
- 2026-09-03
redact strips the identifiers and keeps the transcripts, so the analytics they paid for survive and what remains points at nobody. delete removes the conversations outright - easier to defend, and it takes their own history with it.
A parameter rather than a policy, because the choice is the controller's: it is their lawful basis and their retention obligations, and deciding for them would be us making their compliance decision for them.
Path parameters#
Query parameters#
Headers#
Responses#
Errors#
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.idempotency_key_reused· 422 — This `Idempotency-Key` was used before, for a request with a different body.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-agent limit on top.
More Dashboard endpoints#
Something unclear or missing? Tell us and we’ll fix it.