Preview a session's undo
const url = 'http://127.0.0.1:8080/v1/observe/sessions/example/undo_preview';const options = { method: 'GET', headers: {'Deedglass-Version': '2026-10-01', 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 http://127.0.0.1:8080/v1/observe/sessions/example/undo_preview \ --header 'Authorization: Bearer <token>' \ --header 'Deedglass-Version: 2026-10-01'Free. Plans the undo of every included transaction, newest first, from the row images Postgres committed, and runs S23’s checks without a lock; it never executes. conflicts counts rows that changed again after the session (any conflict blocks the run). sql is the same plan as SQL you review and run yourself, in one transaction, each statement guarded by the values the session left; refusals say why there is no SQL (a TRUNCATE, images past the cap, sensitive columns, expired frames).
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The session (obs_…).
Header Parameters
Section titled “Header Parameters”The API version (YYYY-MM-DD). Leave it out to use your org’s pinned version (public routes use the latest). An unknown version is 400 api_version_invalid.
Query Parameters
Section titled “Query Parameters”Let triggers fire again (the triggers check is then a warning).
Steps to list
Responses
Section titled “Responses”The preview.
object
object
object
object
Rows that changed again after the session.
The undo SQL to review and run yourself (free).
Whether this server may run the undo in one step.
Example
{ "object": "observe_undo_preview"}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
The API version this response follows.
default
Section titled “default”An error. Every error has this envelope; doc_url explains the code.
object
object
One or more calm sentences with the next step.
The request field, query parameter or header the error is about.
On policy_invalid only. Each problem with its line, code and hint.
One finding about a policy file, with its position and the next step. Codes are stable and listed in docs/POLICY_ERRORS.md. In the policy_invalid error envelope each diagnostic also carries object: policy_diagnostic. The full PolicyDiagnostic schema is in openapi.yaml.
object
One agent action. Its sections mirror the deed’s. status is the one field an agent needs; state is the exact lifecycle state (docs/GATE.md). The Gate’s own responses (POST /v1/actions and its result report) add execution.result and witness.reasons; lists leave both out. The full Action schema is in openapi.yaml.
object
On undo_unavailable only. Every check of the undo, each with its fix. Additive (S23).
One of the twelve safety checks (S23 §3.3). Available means no check failed. The full UndoCheck schema is in openapi.yaml.
object
Example
{ "error": { "type": "invalid_request_error", "code": "not_found", "message": "There's no endpoint at GET /v1/helth. Did you mean /v1/health?", "param": null, "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d", "doc_url": "https://docs.deedglass.com/errors/not_found" }}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
The API version this response follows.