Retrieve a Memory Store changedapi/beta/memory_stores/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+18added
Lines−10removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits18to this page, all time
# Retrieve a Memory Store # Retrieve a memory store
The whole hunk
from line 1, old and new numbered
/
from line 1
11---
2title: Retrieve a memory store
2title: Retrieve a Memory Store
33url: https://platform.claude.com/docs/en/api/beta/memory_stores/retrieve
44---
55
6# Retrieve a memory store
6# Retrieve a Memory Store
77
88**GET** `/v1/memory_stores/{memory_store_id}`
99
10Retrieve a memory store
10Retrieve a Memory Store
1111
1212## Path parameters
1313
1414- `memory_store_id: string`
1515
16 ID of the memory store to retrieve (a `memstore_...` identifier). Required. Enumerate IDs via `GET /v1/memory_stores`.
16 The ID of the memory store to retrieve (`memstore_...`).
1717
1818## Headers
1919
from line 147
147147
148148 - `id: string`
149149
150 Unique identifier for the memory store (a `memstore_...` tagged ID). Use this when attaching the store to a session, or in the `{memory_store_id}` path parameter of subsequent calls.
150 The unique ID of the memory store (`memstore_...`). Use it to attach the store to a session.
151151
152152 - `archived_at: string or null`
153153
154 Timestamp when the store was archived, or `null` if active. Set once and never cleared; archiving is one-way. Archived stores are read-only and cannot be attached to new sessions.
154 When the memory store was archived, in RFC 3339, or `null` if it hasn't been.
155155
156 Archiving can't be undone. An archived store can't be attached to new sessions. You can't create or update its memories or update the store. You can still read and delete its memories, redact their versions, and delete the store.
157
158 See the [memory guide](https://platform.claude.com/docs/en/managed-agents/memory?sdk_languages=http#archive-a-store) to learn more about archiving.
159
156160 format: date-time
157161
158162 - `created_at: string`
159163
160 Timestamp when the store was created.
164 When the memory store was created, in RFC 3339.
161165
162166 format: date-time
163167
164168 - `description: string`
165169
166 Free-text description of what the store contains, up to 1024 characters. Included in the agent's system prompt when the store is attached, so word it to be useful to the agent. Empty string when unset.
170 Free-text description of what the store contains, up to 1,024 characters. Included in the agent's system prompt when the store is attached, so word it to be useful to the agent. Empty string when unset.
167171
168172 - `metadata: map[string]`
169173
170 Arbitrary key-value tags for your own bookkeeping (such as the end user a store belongs to). Up to 16 pairs; keys 1–64 characters; values up to 512 characters. Returned on retrieve/list but not filterable.
174 Key-value pairs for your own use, such as the end user that the store belongs to.
171175
176 A store has at most 16 pairs. Keys are 1 to 64 characters long and values at most 512 characters. You can't filter lists by metadata.
177
172178 - `name: string`
173179
174180 Human-readable name for the store. 1–255 characters. The store's mount-path slug under `/mnt/memory/` is derived from this name.
from line 181
175181
176182 - `updated_at: string`
177183
178 Timestamp when the store's `name`, `description`, or `metadata` was last modified. Memory writes inside the store do not advance this.
184 When the memory store was last changed, in RFC 3339.
185
186 Changing its `name`, `description`, or `metadata` updates it. Archiving the store does too. Changes to the store's memories don't.
179187
180188 format: date-time
181189
No line in this hunk matches that.