Skip to main content

​
Endpoint

Erases everything your account holds for one Subject — the full right to be forgotten in a single call: their health records are hard-deleted (rows physically removed), their files and conversations are soft-deleted (gone from the API surface), and the (your account, user) → Subject mapping is dropped so the identity becomes unreachable.
An erase never creates the very Subject it is erasing: resolution looks up the existing mapping only. Passing a user your account has never used returns 404 — nothing is minted.
Response:

​
What gets erased

One call covers the whole /v1 surface for that Subject:
  1. Structured records — everything written via POST /v1/data or stored extractions (POST /v1/extract with store=true), regardless of retention.
  2. Files — everything uploaded via POST /v1/files.
  3. Conversations — stored responses and sessions from the Agent API.
  4. The identity mapping — the Subject itself becomes unreachable. A later request that passes the same user mints a fresh, empty Subject with no connection to the erased one.
For finer-grained deletion, use the per-piece levers instead: DELETE /v1/data (records), DELETE /v1/files/{key} (one file), DELETE /v1/responses/{id} (one stored conversation), DELETE /v1/sessions/{id} (one session’s scope). See Compliance for the full user-rights picture.

​
Errors