PATCH /memories/{memory_id} — Update Memory Content

When a fact about a user changes, you should update the existing memory rather than storing a new one alongside the old. Keeping a single authoritative record prevents your agent from encountering conflicting facts during retrieval. For example, if a user says “I moved from Lagos to Abuja,” find the location memory and patch it — the memory ID is preserved, but the content and its embedding are refreshed so every future search reflects the new truth.

Endpoint: PATCH https://api.remem.online/memories/{memory_id}

Request Headers

Name	Required	Description
`X-API-Key`	Yes	Your Remem API key
`Content-Type`	Yes	`application/json`

Path Parameters

string

required

UUID of the memory you want to update. Obtain this from a previous store, search, or list response.

Query Parameters

string

required

Must match the user_id that owns this memory.

string

required

Must match the agent_id that stored this memory.

Request Body

string

required

The replacement text for this memory. Remem re-embeds the new content automatically so future semantic searches return accurate results.

Examples

curl -X PATCH \
  "https://api.remem.online/memories/775263ee-73af-4416-9804-1f274048ae08?user_id=user_123&agent_id=support_bot" \
  -H "X-API-Key: rm_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "User moved from Lagos to Abuja, Nigeria"
  }'

from remem import RememClient

client = RememClient(api_key="rm_live_xxx")

updated = client.update(
    memory_id="775263ee-73af-4416-9804-1f274048ae08",
    user_id="user_123",
    agent_id="support_bot",
    content="User moved from Lagos to Abuja, Nigeria",
)

print(updated.id)       # same UUID as before
print(updated.content)  # "User moved from Lagos to Abuja, Nigeria"

Response

200 — Success

Returns the full updated Memory object.

{
  "id":          "775263ee-73af-4416-9804-1f274048ae08",
  "content":     "User moved from Lagos to Abuja, Nigeria",
  "user_id":     "user_123",
  "agent_id":    "support_bot",
  "memory_type": "semantic",
  "importance":  0.95,
  "metadata":    {},
  "created_at":  "2026-06-01T10:00:00Z",
  "last_accessed": "2026-06-07T09:00:00Z",
  "expires_at":  null
}

404 — Not Found

{
  "detail": "Memory '775263ee...' not found for user=user_123 agent=support_bot"
}

The memory_id doesn’t exist, or it belongs to a different user_id or agent_id.

Error Responses

Code	Meaning	Fix
`401`	Invalid or missing API key	Verify your key is passed in the `X-API-Key` header
`404`	Memory not found	Check the `memory_id`, `user_id`, and `agent_id` all match the original record
`422`	Validation error	`content` is required in the request body

Remem re-embeds the updated content immediately, so future semantic searches will reflect the change. The memory ID remains unchanged — any references you’ve stored to that ID continue to work.

​Request Headers

​Path Parameters

​Query Parameters

​Request Body

​Examples

​Response

​200 — Success

​404 — Not Found

​Error Responses

Request Headers

Path Parameters

Query Parameters

Request Body

Examples

Response

200 — Success

404 — Not Found

Error Responses