Export the erasure ledger
const url = 'https://example.com/v1/memory/erasures/export';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/v1/memory/erasures/export \ --header 'Authorization: Bearer <token>'The whole ledger, oldest first, content-free: each erasure’s selector kind, the keyed hash of whom it erased, who asked and when. Keep it off-box: restoring a backup rolls the ledger back too, and POST /v1/memory/erasures/replay with it runs the erasures again. Requires admin on the tenant.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The ledger.
object
object
HMAC-SHA256 of the selector under the tenant’s ledger key; absent without one.
Which ledger key made selectorHmac.
waiting-on-run: a turn of the person’s sits in a flow that serves other people; the erasure waits for it (waitingOn) until its deadline, then cancels it.
Example
{ "data": [ { "selectorKind": "fact", "status": "pending" } ]}Missing / malformed / expired / revoked bearer token.
object
object
Stable machine-readable discriminant. Values match domain error codes (see docs/API-ROUTE-CONVENTIONS.md §4.3).
Optional, kind-specific.
object
Server-assigned request id; also echoed via X-Request-Id header.
Examplegenerated
{ "error": { "code": "example", "message": "example", "details": {}, "requestId": "example" }}Not a tenant admin.
object
object
Stable machine-readable discriminant. Values match domain error codes (see docs/API-ROUTE-CONVENTIONS.md §4.3).
Optional, kind-specific.
object
Server-assigned request id; also echoed via X-Request-Id header.
Examplegenerated
{ "error": { "code": "example", "message": "example", "details": {}, "requestId": "example" }}