Get Memory By Id

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.

Use the memory_id returned by creation or listing. Scoped callers cannot use a different query user_id to access another user's memory; an inaccessible record returns 404.

GET/memories/{memory_id}

Retrieve detailed information about a specific user memory by its ID.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Path Parameters

memory_id*Memory Id

Memory ID to retrieve

Query Parameters

user_id?|

User ID to query memory for

db_id?|

Database ID to query memory from

table?|

Table to query memory from

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl --request GET 'https://example.com/memories/string'
{  "memory_id": "f9361a69-2997-40c7-ae4e-a5861d434047",  "memory": "User likes coffee.",  "topics": [    "preferences"  ],  "user_id": "123",  "updated_at": "2025-09-01T07:53:17Z"}