Undo a recovery
/v1/recovery/operations/{operation}/revert in the Disaster Recovery API.
curl -X POST https://api.subscriby.net/v1/recovery/operations/$OPERATION_ID/revert \ -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \ -H "Idempotency-Key: $(uuidgen)" \ -H "Content-Type: application/json" \ -d '{"resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6"}'Inside the undo window (revert_window_ends_at on the operation) a completed recovery can be undone. A channel recovery is undone one swap at a time: resource_id names the resource to put back on its old chat, and every active member is re-admitted there again; the operation reads reverted once its last standing swap is undone. An account relink is undone whole and takes no resource_id: sign-in moves back to the previous account, every browser session is signed out, and a relink_disputed incident opens for support. A bot replacement cannot be undone.
Answers 200 with the operation, its revertible now false. Raises recovery.operation_reverted; a channel undo also moves the resource's place (project.resource.updated with changes.space_id) and an account undo opens the dispute incident (recovery.incident_opened).
Requires ability
The token must hold this ability, or the call is refused with 403.
Delivered to every endpoint subscribed to them once the change is made.
MCP tool
Runs the same action from an agent, behind the same ability.
Idempotent
Send the header on every call; the same key replays the original response for 24 hours.
Authorization
bearerToken A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.
In: header
Path Parameters
The operation, resolved within the ledger by the route binder.
uuidHeader Parameters
A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.
uuidRequest body
JSONWhat the request carriesOptionalapplication/json
Which part of a recovery to undo. A channel recovery is undone one swap at a time and names the resource; an account relink is undone whole and takes an empty body.
Responses
200OKapplication/json
200 with the operation, its undo state updated.
400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json
Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.
401UnauthorizedAUTHENTICATION_REQUIREDapplication/json
The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).
403ForbiddenTOKEN_MISSING_ABILITYapplication/json
The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers FORBIDDEN, TEAM_TIER_REQUIRED or CONNECTOR_TIER_REQUIRED with the same status, and says so in its own description.
404Not foundRESOURCE_NOT_FOUNDapplication/json
An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
On this endpoint: RESOURCE_NOT_FOUND: when resource_id is not a resource the token manages.
409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json
The key was already used in the last 24 hours with a different request body.
422Validation failedVALIDATION_FAILEDapplication/json
The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields.
On this endpoint: VALIDATION_FAILED: for a bot replacement, a channel recovery with no resource_id, a closed window, a swap already put back, or a recovery that is not the token owner's; error.context.operation_id names it.
425Too earlyIDEMPOTENCY_REPLAY_IN_PROGRESSapplication/json
The first request with this key is still running; retry in a few seconds and the original response is replayed.
429Too many requestsRATE_LIMITEDapplication/json
The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.
How is this guide?
Last updated on