Skip to main content
PUT /v1/memory_stores/{memory_store_id}/memories/{memory_id} Updates the content of the specified memory entry. Each update automatically increments the version number and produces a version record.

​
Path parameters

ParameterTypeRequiredDescription
memory_store_idstringYesMemory Store ID with the memstore_ prefix
memory_idstringYesMemory entry ID with the mem_ prefix

​
Headers

HeaderRequiredDescription
AuthorizationYesBearer $QODER_PAT
Content-TypeYesapplication/json

​
Request body

FieldTypeRequiredDescription
contentstringYesNew memory content
versionintegerYesCurrent version number (OCC). Must match the server-side version.

​
Example request

curl -X PUT "https://api.qoder.com/api/v1/cloud/memory_stores/memstore_xxx/memories/mem_xxx" \
  -H "Authorization: Bearer $QODER_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Updated content...",
    "version": 1
  }'

​
Example response

HTTP 200 OK Returns the updated MemoryEntry object. 
{
  "id": "mem_019e3bb965a671fca51bde1cf8d87de0",
  "type": "memory",
  "store_id": "memstore_019e3bb93b7074f9a5130d39ddcca90f",
  "path": "test/note.md",
  "content": "Hello world - updated content",
  "size": 29,
  "content_sha256": "663ab3dd969f51ffd6565202a6a5006db76a96a09a3506962f8d442df8f9bd76",
  "version": 2,
  "metadata": {},
  "created_at": "2026-05-18T15:34:26.494349Z",
  "updated_at": "2026-05-18T15:34:37.780345Z"
}

​
Response fields

FieldTypeDescription
idstringUnique identifier
typestringAlways "memory"
store_idstringOwning Memory Store ID
pathstringRelative path (unchanged)
contentstringUpdated content
sizeint64New content size in bytes
content_sha256stringSHA-256 hash of the new content
versionint64Incremented version number
metadataobjectCustom metadata
created_atstringOriginal creation time (unchanged)
updated_atstringUpdate time (ISO 8601)

​
Errors

HTTPTypeTrigger
401TOKEN_INVALIDMissing or invalid authentication token
404not_found_errorMemory Store or memory entry does not exist
409conflict_errorversion mismatch (concurrent modification)

​
Notes

  • Each update increments version automatically (e.g., 1 → 2).
  • created_at is unchanged; updated_at is set to the current time.
  • size and content_sha256 are recomputed from the new content.
  • Each update produces a version record with action: "updated".
  • path cannot be changed during update.
See Errors for the full error envelope.