Undo a change
POST/v1/changes/{changeId}/revert
Undoes a change, as Undo does, and needs the permissions of the operation that made it. It is conditional: if anything the change touched was edited since, it refuses with a 409 and changes nothing (the change stays applied). If a LATER step is refused, the change becomes failed and the error says partial: true. Only an applied change can be undone, and an undo cannot itself be undone: make the change again.
Permissions: any valid key · Kind: write · Cost: 1 unit · MCP tool undo_change
Cannot be undone.
Path parameters
| Field | Type | Required | Description |
|---|---|---|---|
changeId |
uuid | yes |
Body
None.
Response 200
| Field | Type | Required | Description |
|---|---|---|---|
object |
"change" | yes | |
id |
uuid | yes | |
operationId |
string | yes | |
surface |
"rest" | "mcp" | yes | |
status |
"applying" | "applied" | "failed" | "reverting" | "reverted" | yes | |
tripIds |
string[] | yes | |
credentialId |
string | null | yes | |
error |
string | null | yes | |
createdAt |
string | yes | |
updatedAt |
string | yes | |
revertedAt |
string | null | yes |
Errors
Errors are problem details. Besides the refusals described above, any call like this one can return:
invalid_request— Invalid requestunauthorized— Missing or invalid API keyinsufficient_scope— Missing permissionrate_limited— Rate limit reachednot_found— Not foundidempotency_key_reused— Idempotency-Key reusedrequest_in_progress— Request in progress