Link two already-stored accessible items as a supersession.
SVC-SUPERSEDE-LINK-1. The sibling POST /{item_id}/supersede creates the
replacement from a content payload. This one relates two records that already
exist, which is what a caller that wrote them separately needs.
item_id is the OLD item, matching the sibling route's convention.
The write stamps the OLD node with superseded=True, superseded_by and
superseded_at, so consumers detect supersession by reading those
properties off a recalled record, never by scanning for inbound edges.
Send Authorization: Bearer <token>. The token is either a Clerk session JWT or a SmartMemory API key (prefix sm_live_, sm_test_, or legacy sk_).
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Relate two items that already exist (SVC-SUPERSEDE-LINK-1).
Distinct from SupersedeMemoryRequest, which carries the content of a
replacement to be created. Here both records are already stored.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/memory/string/supersede-link" \ -H "Content-Type: application/json" \ -d '{ "new_item_id": "string" }'{
"status": "scheduled",
"old_item_id": "string",
"new_item_id": "string",
"scope_go_lives": [
{}
],
"recorded_at": "2019-08-24T14:15:22Z"
}{
"detail": {
"code": "invalid_scoped_validity",
"message": "string",
"retryable": false
}
}{
"detail": {
"code": "invalid_scoped_validity",
"message": "string",
"retryable": false
}
}{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}{
"detail": {
"code": "invalid_scoped_validity",
"message": "string",
"retryable": false
}
}