Skip to main content
DELETE
Erase a subject (GDPR path)
Full per-subject erasure: tenant rows, mapping, internal user. Idempotent 204.

Authorization

This route requires the subjects:provision scope. A key carrying admin also qualifies. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Beyond the shared statuses, this route can answer with subject_mapping_invalid. Every problem body names its own code, and the type URI always resolves to the matching page. Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Notes

  • This is the documented erasure path for an end user. It removes the subject’s rows, its mapping and its internal user, then deletes its uploaded imports and export documents from storage.
  • The organization’s brain is marked stale, not deleted. It is trained across every subject, so it is retrained rather than destroyed.
  • Idempotent 204. Erasing a subject that is already gone succeeds.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Path Parameters

subject_id
string
required

Developer-supplied subject id: 1-128 chars of [A-Za-z0-9._:-].

Response

Successful Response