Retrieve a Memory changedapi/beta/memory_stores/memories/retrieve
Nearest release: v2.1.306, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+26added
Lines−10removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits19to this page, all time
# Retrieve a Memory # Retrieve a memory
The whole hunk
from line 1, old and new numbered
/
from line 1
11---
2title: Retrieve a memory
2title: Retrieve a Memory
33url: https://platform.claude.com/docs/en/api/beta/memory_stores/memories/retrieve
44---
55
6# Retrieve a memory
6# Retrieve a Memory
77
88**GET** `/v1/memory_stores/{memory_store_id}/memories/{memory_id}`
99
10Retrieve a memory
10Retrieve a Memory
1111
1212## Path parameters
1313
from line 23
2323
2424- `view: optional BetaManagedAgentsMemoryView`
2525
26 Selects which projection of a `memory` or `memory_version` the server returns. `basic` returns the object with `content` set to `null`; `full` populates `content`. When omitted, the default is endpoint-specific: retrieve operations default to `full`; list, create, and update operations default to `basic`. Listing with `view=full` caps `limit` at 20.
26 Whether a `memory` or `memory_version` in the response includes its `content`. Defaults to `full` on retrieve operations and to `basic` on list, create, and update operations.
2727
28 With `full`, list operations return at most 20 items per page.
29
2830 - `"basic"`
2931
3032 Return the object with `content` set to `null`. The `content_size_bytes` and `content_sha256` fields remain populated, so sync clients can diff without fetching content.
from line 161
159161
160162- `BetaManagedAgentsMemory object`
161163
162 A `memory` object: a single text document at a hierarchical path inside a memory store. The `content` field is populated when `view=full` and `null` when `view=basic`; the `content_size_bytes` and `content_sha256` fields are always populated so sync clients can diff without fetching content. Memories are addressed by their `mem_...` ID; the path is the create key and can be changed via update.
164 A text document at a path inside a memory store.
163165
166 `content` is `null` when the response uses `view=basic`. `content_size_bytes` and `content_sha256` are always set, so you can detect changes without fetching the content. To retrieve, update, or delete a memory, pass its ID, which stays the same when its path changes.
167
168 See the [memory guide](https://platform.claude.com/docs/en/managed-agents/memory?sdk_languages=http#view-and-edit-memories) to learn more about working with memories.
169
164170 - `type: "memory"`
165171
166172 - `id: string`
167173
168 Unique identifier for this memory (a `mem_...` value). Stable across renames; use this ID, not the path, to read, update, or delete the memory.
174 The unique ID of the memory (`mem_...`). It stays the same when the memory's path changes.
169175
176 To retrieve, update, or delete the memory, pass this ID.
177
170178 - `content_sha256: string`
171179
172180 Lowercase hex SHA-256 digest of the UTF-8 `content` bytes (64 characters). The server applies no normalization, so clients can compute the same hash locally for staleness checks and as the value for a `content_sha256` precondition on update. Always populated, regardless of `view`.
from line 181
173181
174182 - `content_size_bytes: number`
175183
176 Size of `content` in bytes (the UTF-8 plaintext length). Always populated, regardless of `view`.
184 The size of the memory's `content` in UTF-8 bytes. It is set regardless of `view`.
177185
178186 format: int32
179187
from line 197
189197
190198 - `memory_version_id: string`
191199
192 ID of the `memory_version` representing this memory's current content (a `memver_...` value). This is the authoritative head pointer; `memory_version` objects do not carry an `is_latest` flag, so compare against this field instead. Enumerate the history via [List memory versions](https://platform.claude.com/docs/en/api/beta/memory_stores/memory_versions/list?sdk_languages=http).
200 The ID of the memory version that holds the memory's current content (`memver_...`).
193201
202 Memory versions don't have a flag that marks the latest one. Compare their IDs with this field instead.
203
204 See the [memory guide](https://platform.claude.com/docs/en/managed-agents/memory?sdk_languages=http#audit-memory-changes) to learn more about memory versions.
205
194206 - `path: string`
195207
196208 Hierarchical path of the memory within the store, e.g. `/projects/foo/notes.md`. Always starts with `/`. Paths are case-sensitive and unique within a store. Maximum 1,024 bytes.
from line 209
197209
198210 - `updated_at: string`
199211
200 When this memory was last modified, in RFC 3339 format. Use this as a cheap freshness signal; for who made the change, look up the head version's `created_by` via [List memory versions](https://platform.claude.com/docs/en/api/beta/memory_stores/memory_versions/list?sdk_languages=http).
212 When the memory was last changed, in RFC 3339.
201213
214 To find out who made the change, look at `created_by` on the memory version that `memory_version_id` references.
215
202216 format: date-time
203217
204218 - `content: optional string or null`
205219
206 The memory's UTF-8 text content. Populated when `view=full`; `null` when `view=basic`. Maximum 100 kB (102,400 bytes).
220 The memory's UTF-8 text content, or `null` when the response uses `view=basic`.
221
222 The maximum size is 100 kB (102,400 bytes).
207223
208224## Example
209225
No line in this hunk matches that.