Delete Caller (GDPR purge)

Soft-delete the caller AND cascade soft-delete every memory row pointing at it. Conversations survive (forensic / billing records) but their caller pointer surfaces as “deleted” through the API.

Idempotent — re-deleting an already-purged caller returns {caller_purged: 0, memories_purged: 0}. Audit row counts accompany every response so a privacy operator has direct evidence of the purge without re-querying.

Soft-delete the caller AND cascade soft-delete every memory row pointing at it. Conversations survive (forensic / billing records) but their caller pointer surfaces as "deleted" through the API. Idempotent — re-deleting an already-purged caller returns `{caller_purged: 0, memories_purged: 0}`. Audit row counts accompany every response so a privacy operator has direct evidence of the purge without re-querying.

Authentication

AuthorizationBearer

Enter your API key with the Bearer prefix, e.g. ‘Bearer sk_…’.

Path parameters

idstringRequired

Response

Soft-delete completed; row counts in the body.

caller_purgedinteger

1 on the first delete; 0 on idempotent re-delete.

memories_purgedinteger

Number of user_memories rows cascade-soft-deleted under this caller.