VocalDocscontracts 1.65.0

Purge a Contact's data

POST /v1/contacts/{contact_id}/purge

PropertyValue
Operationpurge_contact
GroupContacts
Scopecontacts:write
Route classcontrol
IdempotencyIdempotency-Key accepted: a retry with the same key replays the first answer
AuditAudited contacts.contact.purge (mutation)
Released in1.61.0
Phase 0 hostServed (the hosted api pins 1.65.0)

Deletes a Contact's profile, identity values and external ids at once (1.61.0; section 5.2), whatever its status, writes contact.purged, and answers what remains and why: consent records keyed by address hash, which survive an erasure request (ADR 0050, OQ-68), Audit events, and Calls whose contact_id no longer resolves.

Request

Set VOCAL_API to the base URL of your API and VOCAL_API_KEY to an API key with the contacts:write scope (Authentication and keys). Replace each placeholder, such as agt_... or <name>, with your own value.

curl -X POST "$VOCAL_API/v1/contacts/ctc_.../purge" \
  -H "Authorization: Bearer $VOCAL_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

Parameters

NameInTypeRequiredDescription
contact_idpathContactIdyesThe id of a Contact: ctc_ and the row's UUIDv7 in 26 Crockford base32 characters. Opaque and safe to log.
idempotency-keyheaderstringnoA client-chosen key, kept 24 hours per Organization, environment and route. A replay returns the stored response.

Responses

StatusContent typeShapeError codes
200application/jsonContactPurge
400application/jsonErrorEnvelopeinvalid_request
401application/jsonErrorEnvelopeunauthenticated
403application/jsonErrorEnvelopeforbidden, org_suspended
404application/jsonErrorEnvelopenot_found
409application/jsonErrorEnvelopeidempotency_in_progress, idempotency_key_reused
429application/jsonErrorEnveloperate_limited
500application/jsonErrorEnvelopeinternal_error

Fields of the 200 answer

The shape is ContactPurge.

FieldTypeRequiredDescription
contact_idContactIdyes
object"contact_purge"yes
purged_atTimestampyes
remainsarray of ContactPurgeRemainderyes