Get a specific memory

POST 
/api/v1/llm/get-memory

Requests a memory by ID. Full project/user ownership checks are not currently enforced for these by-ID operations. They are not a supported access boundary for an untrusted end-user client. See Memory for the current limits.

The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized scoped domain action.

Use this in a guide: Use remembered preferences in a returning user’s conversation

Request

Responses

200

Memory returned

Schema-valid request illustration; replace example identifiers and confirm operation prerequisites.

Section ID: DOC-MA-conversations-api-getMemory#example-conversations-getMemory-request

Request example

{
  "memoryId": "example_123"
}

Guide request for Inspect the selected record before changing it. Replace example resource identifiers with your own authorized values.

Section ID: DOC-MA-conversations-api-getMemory#example-cookbook-managed-agents-memory-knowledge-index-03-request

Request example

{
  "memoryId": "mem_abc123"
}

Illustrative response shape; omitted default fields and actual outcomes depend on the operation.

Section ID: DOC-MA-conversations-api-getMemory#example-conversations-getMemory-response

Response example

{
  "memory": {
    "id": "example_123",
    "memory": "example",
    "userId": "example_123",
    "agentId": "example_123",
    "appId": "example_123",
    "runId": "example_123",
    "metadata": {},
    "score": 1,
    "createdAt": "2026-09-16T12:00:00Z",
    "updatedAt": "2026-09-16T12:00:00Z"
  }
}

Document ID: DOC-MA-conversations-api-getMemory. Section identities and revisions.

Section	Stable reference
Get a specific memory	DOC-MA-conversations-api-getMemory#overview
Request	DOC-MA-conversations-api-getMemory#request
Responses	DOC-MA-conversations-api-getMemory#responses