Forget an entire scope
Delete every fact in one scope. Returns immediately; the purge runs in batches in the background, so a list right afterwards can still show rows.
This does not touch collections — DELETE /v1/memory/collections/{collection} does that.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Query Parameters
Which scope to address: contact:<contactId>, conversation:<conversationId>, or omitted for the project scope.
Note the asymmetry with POST /v1/memory and POST /v1/memory/search, which take the scope in the request BODY as scope plus contactId/conversationId. Every other Memory endpoint takes it here.
Scope as a query-string value: contact:<contactId>, conversation:<conversationId>, the literal project, or omitted for project scope.
Only the SHAPE of the id is validated, never its existence — the partition already carries your project, so an id that matches nothing simply addresses an empty scope rather than returning 404.
"contact:jd7x2k3m4n5p6q7r8s9t0abc"
Response
Purge scheduled.
"deleting"
