The whole hunk
from line 1, old and new numbered
/
lines
from line 1
1---
2title: Update a memory
3url: https://platform.claude.com/docs/en/api/beta/memory_stores/memories/update
4---
5
16# Update a memory
27
38**POST** `/v1/memory_stores/{memory_store_id}/memories/{memory_id}`
from line 33
2833
2934 - `string`
3035
31 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 41 more`
36 - `"message-batches-2024-09-24" or "prompt-caching-2024-07-31" or "computer-use-2024-10-22" or 42 more`
3237
3338 - `"message-batches-2024-09-24"`
3439
from line 81
7681
7782 - `"user-profiles-2026-08-18"`
7883
84 - `"user-profiles-2026-09-04"`
85
7986 - `"advisor-tool-2026-03-01"`
8087
8188 - `"managed-agents-2026-04-01"`
from line 125
118125
119126 - `"mid-conversation-system-clear-at-2026-08-21"`
120127
128- `"anthropic-workspace-id": optional string`
129
121130## Body parameters
122131
123132- `content: optional string or null`
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 188
177188 - `path: string`
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.
180
181 - `type: "memory"`
182191
183192 - `updated_at: string`
184193