Get an incident

curl https://api.subscriby.net/v1/recovery/incidents/$INCIDENT_ID \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

One incident.

reason is the connector's own code for what it saw; reason_label and reason_explanation are that code in the connector's words, the same sentence the alert email carried. Both are null when the probe recorded no reason, which is the case for account incidents.
resource_id and resource_title are set on resources incidents only; project_id is null on an account incident.

Requires ability

project-recovery:view

The token must hold this ability, or the call is refused with 403.

Authorization

bearerToken

AuthorizationBearer <token>

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

incident*string

The incident, resolved within the ledger by the route binder.

Formatuuid

Responses

200OKapplication/json

200 with the incident.

data*

The response's payload.

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).

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

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.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X GET "https://example.com/v1/recovery/incidents/497f6eca-6276-4993-bfeb-53cbbbba6f08"

{  "data": {    "id": "6f1e9b27-4c3a-4d58-9e02-b7a1c5d38f64",    "kind": "resources",    "kind_label": "Channels and Groups",    "status": "open",    "status_label": "Open",    "connector": "telegram",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "project_name": "Research Premium",    "resource_id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6",    "resource_title": "Signals",    "reason": "chat_not_found",    "reason_label": "Channel not found",    "reason_explanation": "**Most likely cause:** the platform deleted or banned the channel. Replace it with a new one.",    "detected_at": "2026-09-12T03:19:04Z",    "resolved_at": null,    "resolved_by_operation_id": null  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: RecoveryIncidentResource;}export interface RecoveryIncidentResource {  id: string;  kind: string;  kind_label: string;  status: string;  status_label: "Open" | "Resolved";  connector: string | null;  project_id: string | null;  project_name: string | null;  resource_id: string | null;  resource_title: string | null;  reason: string | null;  reason_label: string | null;  reason_explanation: string | null;  detected_at: string;  resolved_at: string | null;  resolved_by_operation_id: string | null;}

Get an incident

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Authorization

Path Parameters

Responses