ZAzavudev
Memory

Forget a fact

Changed on

Delete one fact. Idempotent: deleting a fact that is not there, or no longer there, still answers 204. Deletes are never refused for quota reasons.

delete/v1/memory/{memoryId}

Request

  • Base URL
    https://api.zavu.dev
  • URL
    https://api.zavu.dev/v1/memory/{memoryId}
  • Auth
    HTTP bearer

Path parameters

memoryIdstring required

Memory (fact) ID.

Query parameters

scopestring

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.

Example:contact:jd7x2k3m4n5p6q7r8s9t0abc

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.

Response

Fact deleted.

Changes