Archive a Memory Store changedapi/beta/memory_stores/archive
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+20added
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
# Archive a Memory Store # Archive a memory store
The whole hunk
from line 1, old and new numbered
/
from line 1
11---
2title: Archive a memory store
2title: Archive a Memory Store
33url: https://platform.claude.com/docs/en/api/beta/memory_stores/archive
44---
55
6# Archive a memory store
6# Archive a Memory Store
77
88**POST** `/v1/memory_stores/{memory_store_id}/archive`
99
10Archive a memory store
10Archive a Memory Store
1111
1212## Path parameters
1313
1414- `memory_store_id: string`
1515
16 ID of the memory store to archive (a `memstore_...` identifier). Required. Archiving is one-way and idempotent; archived stores cannot be unarchived. Enumerate IDs via `GET /v1/memory_stores`.
16 The ID of the memory store to archive (`memstore_...`).
1717
18 Archiving can't be undone. Archiving a store that is already archived returns it unchanged.
19
1820## Headers
1921
2022- `"anthropic-version": optional string`
from line 149
147149
148150 - `id: string`
149151
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.
152 The unique ID of the memory store (`memstore_...`). Use it to attach the store to a session.
151153
152154 - `archived_at: string or null`
153155
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.
156 When the memory store was archived, in RFC 3339, or `null` if it hasn't been.
155157
158 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.
159
160 See the [memory guide](https://platform.claude.com/docs/en/managed-agents/memory?sdk_languages=http#archive-a-store) to learn more about archiving.
161
156162 format: date-time
157163
158164 - `created_at: string`
159165
160 Timestamp when the store was created.
166 When the memory store was created, in RFC 3339.
161167
162168 format: date-time
163169
164170 - `description: string`
165171
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.
172 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.
167173
168174 - `metadata: map[string]`
169175
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.
176 Key-value pairs for your own use, such as the end user that the store belongs to.
171177
178 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.
179
172180 - `name: string`
173181
174182 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 183
175183
176184 - `updated_at: string`
177185
178 Timestamp when the store's `name`, `description`, or `metadata` was last modified. Memory writes inside the store do not advance this.
186 When the memory store was last changed, in RFC 3339.
187
188 Changing its `name`, `description`, or `metadata` updates it. Archiving the store does too. Changes to the store's memories don't.
179189
180190 format: date-time
181191
No line in this hunk matches that.