Delete Multiple Memories

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.

Send a JSON body with a nonempty memory_ids array and optional user_id:

{"memory_ids":["returned-memory-id"],"user_id":"example-user"}

An empty array returns 422, despite the generated 400 description. 204 does not prove that every supplied ID existed or was visible; only matching records in the effective user scope are deleted.

DELETE/memories

Delete multiple user memories by their IDs in a single operation. This action cannot be undone and all specified memories will be permanently removed.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Query Parameters

db_id?|

Database ID to use for deletion

table?|

Table to use for deletion

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

curl --request DELETE 'https://example.com/memories' \  --header 'Content-Type: application/json' \  --data-raw '{"memory_ids":["string"]}'
Empty