List memories changedapi/beta/memory_stores/memories/list
Nearest release: v2.1.268, published under an hour 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+14added
Lines−5removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits23to this page, all time
The whole hunk
from line 1, old and new numbered
/
from line 1
1---
2title: List memories
3url: https://platform.claude.com/docs/en/api/beta/memory_stores/memories/list
4---
5
16# List memories
27
38**GET** `/v1/memory_stores/{memory_store_id}/memories`
from line 51
4651
4752 - `string`
4853
49 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 41 more`
54 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 42 more`
5055
5156 - `"message-batches-2024-09-24"`
5257
from line 99
9499
95100 - `"user-profiles-2026-08-18"`
96101
102 - `"user-profiles-2026-09-04"`
103
97104 - `"advisor-tool-2026-03-01"`
98105
99106 - `"managed-agents-2026-04-01"`
from line 143
136143
137144 - `"mid-conversation-system-clear-at-2026-08-21"`
138145
146- `"anthropic-workspace-id": optional string`
147
139148## Returns
140149
141150- `data: optional array of BetaManagedAgentsMemoryListItem`
from line 155
146155
147156 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.
148157
158 - `type: "memory"`
159
149160 - `id: string`
150161
151162 Unique identifier for this memory (a `mem_...` value). Stable across renames; use this ID, not the path, to read, update, or delete the memory.
from line 189
178189
179190 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.
180191
181 - `type: "memory"`
182
183192 - `updated_at: string`
184193
185194 A timestamp in RFC 3339 format
from line 203
194203
195204 A rolled-up directory marker returned by [List memories](/docs/en/api/beta/memory_stores/memories/list) when `depth` is set. Indicates that one or more memories exist deeper than the requested depth under this prefix. This is a list-time rollup, not a stored resource; it has no ID and no lifecycle. Each prefix counts toward the page `limit` and interleaves with `memory` items in path order.
196205
206 - `type: "memory_prefix"`
207
197208 - `path: string`
198209
199210 The rolled-up path prefix, including a trailing `/` (e.g. `/projects/foo/`). Pass this value as `path_prefix` on a subsequent list call to drill into the directory.
200
201 - `type: "memory_prefix"`
202211
203212- `next_page: optional string or null`
204213
No line in this hunk matches that.