Delete Memory

Database and user

Use a registered memory-capable database, such as the SQLite database in the example API server. Supply db_id when several database IDs are available. A table selector requires db_id and selects a configured adapter; it does not create arbitrary storage.

Scoped identity overrides a supplied user_id. JWT user isolation is opt-in; non-admin service-account PAT callers always self-scope. When authorization is enforced, use the appropriate memories:read, memories:write or memories:delete scope.

A 204 response can also cover a missing memory. It does not establish that a row existed before the request. Scoped deletion applies only to the caller's memories.

DELETE/memories/{memory_id}

Permanently delete a specific user memory. This action cannot be undone.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Path Parameters

memory_id*Memory Id

Memory ID to delete

Query Parameters

user_id?|

User ID to delete memory for

db_id?|

Database ID to use for deletion

table?|

Table to use for deletion

Response Body

application/json

application/json

application/json

application/json

application/json

curl --request DELETE 'https://example.com/memories/string'
Empty