Disaster Recovery API

Everything the Disaster Recovery pages show a creator is readable here: what the health probes found broken, what was done about it and whether it can still be undone, how many members a channel recovery has re-admitted so far, how many self-service recoveries the rolling window still allows, and how ready the account is for the next ban. And everything a creator does about it afterwards is here too: the per-project settings, the standbys kept ready, the two requests that start a chat picker on the connector, the undo, the reminder to stragglers, the handover mail after a bot replacement, and the member list to keep before one.

The ledger endpoints live under /v1/recovery with no project in the path because the ledger belongs to the account holder, not to a project: a ban lands on the creator's sign-in account and on every project at once. Settings and standbys hang off the project and the resource they concern. The creator's own account lives under /v1/me/recovery.

Background

TenancyCopy Anchor Link

The ledger a token reads is the one of the creator who owns the team the token is scoped to. A teammate holding project-recovery:view-any therefore reads the same rows the owner sees on the dashboard; a token scoped to another team sees none of them, and any id from another creator's ledger is 404 RESOURCE_NOT_FOUND.

Reads are the team's, writes are the owner's. The writes run the same actions the dashboard runs, and those refuse anyone but the project owner (or, for the account, the account holder) with 422 VALIDATION_FAILED and the reason, the same sentence the dashboard would show. Registering a standby installation and replacing the project bot take a credential and stay off tokens altogether.

Every enum value comes with its label beside it (kind_label, status_label, reason_label), the same words the dashboard shows, so a client can render the ledger without a translation table of its own.

EndpointsCopy Anchor Link

Related

Disaster Recovery ProgramWhat the program does and why.History and UndoThe same ledger on the dashboard.Active Disaster PreventionThe features the readiness lines check.Allowances and Support ReviewThe quota rule and what support audits before releasing a grant.recovery.* eventsThe Disaster Recovery ledger as it moves: incidents opening and resolving, recoveries starting, finishing, failing and being undone, standbys kept and consumed, channels swapped and accounts relinked.Ability CatalogEvery ability string a token can carry, what enforces it on the API and the MCP server, and how to pick the right ones when minting.