List recovery operations
curl "https://api.subscriby.net/v1/recovery/operations?kind=resources&status=completed" \
-H "Authorization: Bearer $SUBSCRIBY_TOKEN"
An operation is one recovery: run by the creator, by the platform on their behalf (automatic: true, the failover you sleep through), or on demand (on_demand: true, a Swap & Grant of a healthy resource, which spends no allowance). The row exists from the moment the recovery starts, because it is the quota ledger and the audit trail at once.
Both filters are optional: kind is account, bot or resources; status is started, completed, failed or reverted. Newest first by started_at; sort_by also accepts kind, status and completed_at.
Request
- Base URL: https://api.subscriby.net
- URL: https://api.subscriby.net/v1/recovery/operations
- Auth: HTTP bearer
Query parameters
The three things a platform ban can take from a creator, and the three recoveries the Disaster Recovery Program offers for them. Declared in wizard order. The account comes first because a creator whose own identity is gone cannot act on the connector for the other two until it is replaced; the installation before the resources because customers must be able to reach it before they are re-admitted anywhere. The backing value is also the quota key: RecoveryPolicyService counts operations per kind, so a creator who used one kind still has the other two available inside the same window. The words a creator reads come from the connector's vocabulary, so the same case reads "Project Bot" for one connector and "Project App" for another; callers without a vocabulary at hand go through ConnectorRecoverySupport::issueLabel().
Narrow to one kind: account, bot or resources. An unknown value is refused.
Where a recovery operation stands. Started and Completed both count against the self-service quota: an operation is a use the moment it begins, so an abandoned wizard cannot be restarted for free. Failed is the one state that gives the use back, because nothing changed. Reverted records that the creator undid the change inside the undo window; the use stays consumed.
Narrow to one status: started, completed, failed or reverted. An unknown value is refused.
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.
Rows per page, 1 to 100. A higher value clamps to the cap silently. Defaults to 25.
The column to order by. Defaults to started_at; a column the endpoint does not offer falls back to the default rather than failing.
asc or desc. Defaults to desc.
Response
The page, newest first by default.
Example response
{
"data": [
{
"id": "9a4d2e71-5b38-4c6f-8e12-3d7c9b0a5f21",
"kind": "resources",
"kind_label": "Channels and Groups",
"status": "completed",
"status_label": "Completed",
"connector": "telegram",
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"project_name": "Research Premium",
"automatic": true,
"started_at": "2026-09-12T03:19:10Z",
"completed_at": "2026-09-12T03:19:42Z",
"revertible": true,
"revert_window_ends_at": "2026-09-13T03:19:42Z"
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.