Disaster Recovery

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.
get/v1/recovery/incidents/{incident}

Request

  • Base URL: https://api.subscriby.net
  • URL: https://api.subscriby.net/v1/recovery/incidents/{incident}
  • Auth: HTTP bearer

Path parameters

incidentstring uuid required

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

Response

200 with the incident.

Example response

{
  "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"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.