List incidents
/v1/recovery/incidents in the Disaster Recovery API.
curl "https://api.subscriby.net/v1/recovery/incidents?status=open" \ -H "Authorization: Bearer $SUBSCRIBY_TOKEN"An incident is one problem a probe detected and has not yet seen fixed: the creator's sign-in account unreachable (kind: account), a project's bot refused by the platform (bot), or a channel or group the project sells gone or no longer administered (resources). It resolves itself when a later probe finds the thing healthy, or is resolved by the recovery that replaced it, which resolved_by_operation_id then names.
status is open (the default: what still needs attention), resolved, or all. Paginated like every list, newest first by detected_at; sort_by also accepts kind, status and resolved_at.
Requires ability
The token must hold this ability, or the call is refused with 403.
MCP tool
Runs the same action from an agent, behind the same ability.
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
Query Parameters
The tab: open (the default, what still needs attention), resolved, or all.
The 1-based page to return. A page past the last answers an empty data array with meta.total still filled, so a loop can stop without guessing.
1 <= value1Rows per page, 1 to 100. A higher value clamps to the cap silently. Defaults to 25.
1 <= value <= 10025The column to order by. Defaults to detected_at; a column the endpoint does not offer falls back to the default rather than failing.
"detected_at"asc or desc. Defaults to desc.
"desc"Value in
- "asc"
- "desc"
Responses
200OKapplication/json
The page, newest first by default.
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.
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: when status is not open, resolved or all.
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