Skip to main content
DELETE
Remove (tombstone) an edge
Tombstone an edge whose endpoints the effective subject owns. Idempotent. Edges carry no reliable owner of their own, so ownership is proven by requiring the subject to own both endpoint nodes. Removal writes a tombstone rather than deleting the row, mirroring node forget, so the removal stays auditable and reversible while graph reads filter the edge out. An edge the subject cannot fully see returns 404.

Authorization

This route requires the memory:forget scope. A key carrying write also qualifies. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Notes

  • Ownership is proven by both endpoints. Edges carry no reliable owner of their own, so the effective subject must own the source node and the target node. An edge you cannot fully see is 404.
  • This is a tombstone, mirroring node forget, so it is auditable and reversible in the graph read paths.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Path Parameters

edge_id
string
required

The graph edge id.

Response

Successful Response

Tombstone acknowledgement for a node/edge forget.

id
string
required
deleted
boolean
default:true
tombstoned
boolean
default:true
undeleteWindowDays
integer
default:30