Contexts

Restore a context to a prior version_seq (T710)

Forward-only: internally calls the same update path a normal edit uses, so the restore itself is written as a NEW context_versions row (history is append-only, nothing is deleted or rewound) and the usual auto-index/auto-embed hooks fire. Rejects a redacted snapshot (one whose content was overwritten by a GDPR erasure) with 409 rather than restoring erased text.

post/api/contexts/{id}/versions/{seq}/restore

Request

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

Path parameters

idinteger required
seqinteger required

The versionSeq to restore, as returned by GET .../versions.

Response

Context updated to the restored snapshot's content.

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.