Skip to main content
GET
Get a memory entry by ID
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

GET /api/v2/memory/get?id=<memoryId>&layer=<channel|longterm> answers one ChannelMemoryEntry or LongTermMemoryEntry. A forgotten long-term entry is still returned, with status: "FORGOTTEN", so a caller can observe a delete. A missing memory, one whose agent is outside the caller’s reach (an External App’s owner-scope chain; for an API key, memory:read at the agent’s home) or is a Personal Agent, and one stamped with a company the caller can’t read all answer 404 resource_missing, so a refusal never tells a foreign memory from a missing one.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Path Parameters

memoryId
string
required

Query Parameters

layer
enum<string>
default:channel

Memory layer: channel (per-channel institutional memory) or longterm (RAG-indexed durable archive). Defaults to channel when omitted. Any other value answers 400 layer_not_supported.

Available options:
channel,
longterm

Response

Memory entry detail

data
object
required
meta
object
required