Contexts

Update a context (partial — omitted fields are left unchanged)

put/api/contexts/{id}

Request

  • Base URL: http://localhost:38200
  • URL: http://localhost:38200/api/contexts/{id}
  • Auth: one of:
    • HTTP bearer
    • API key in cookie token

Path parameters

idinteger required

Request body

namestring
descriptionstring
contentstring
type'reference' | 'feedback' | 'project' | 'incident' | 'lesson' | 'user' | 'synthesis' | 'map' | 'moc' | 'handoff' | 'endpoint' | 'trail'
scope'personal' | 'workspace' | 'team'
tagsstring[]
metadataobject
propertiesobject
archivedAtstring date-time nullable
lifecycle'fleeting' | 'working' | 'evergreen' | 'archived'
memoryClass'action' | 'knowledge'
memoryKind'episodic' | 'semantic' | 'procedural'
valid_fromstring date-time nullable
valid_tostring date-time nullable
atomicboolean
importanceScorenumber nullable

Response

Updated context.

idinteger
namestring
descriptionstring
contentstring
type'reference' | 'feedback' | 'project' | 'incident' | 'lesson' | 'user' | 'synthesis' | 'map' | 'moc' | 'handoff' | 'endpoint' | 'trail'
scope'personal' | 'workspace' | 'team'
workspacestring nullable
projectstring nullable
lifecyclestring
tagsstring[]
metadataobject
createdAtstring date-time
updatedAtstring date-time
mergedIntointeger nullable

T743, additive. Present ONLY on the response of POST /api/contexts when the T711 near-duplicate guard folded this write into an EXISTING row instead of inserting a new one -- the id of that existing (surviving) row, which is also id above. Absent/undefined on every other response shape (search, list, get, update) and on a genuine create. A caller that sees mergedInto set knows no new row was created and should treat the write as an update to the returned id, not a create.

Changes

No recorded changes to this operation across all 1 revision of this API.