---
title: "A recovery began: run by the creator, by the platform on their behalf, or on demand for a healthy resource."
method: POST
path: "recovery.operation_started"
tags: ["recovery.* events"]
---

# A recovery began: run by the creator, by the platform on their behalf, or on demand for a healthy resource.

`POST recovery.operation_started` (webhook)

### When this fires

The moment a recovery is opened in the ledger: an account relink or a switch to the backup account, a bot replacement, or a channel swap. The row exists from this moment because it is the quota ledger too: the allowance is spent here, and given back only if the recovery fails before changing anything.

A channel recovery absorbs every swap made inside its grace period into one operation, so a second channel swapped an hour after the first fires no second start; it fires `recovery.resource_replaced` under the same `operation_id`.

### Caveats

- Once per operation. Swaps absorbed into a running channel recovery fire no second start.
- A recovery refused before the ledger row is written (quota spent, not the owner, plan lacks the feature) fires nothing.

### Related events

- `recovery.operation_completed`, `recovery.operation_failed`: how it ends.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'recovery.operation_started', required: The event name, always `recovery.operation_started` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `operation_id` string, uuid, required: The operation; read it with [the operation endpoint](https://docs.subscriby.net/api/v1/reference/disaster-recovery).
    - `kind` 'account' | 'bot' | 'resources', required: What the recovery acts on.
    - `connector` string, nullable, required: The connector the recovery acts on.
    - `project_id` string, uuid, nullable, required: The project, or null for an account recovery.
    - `automatic` boolean, required: True when the platform ran it without the creator (automatic failover).
    - `on_demand` boolean, required: True for a Swap & Grant of a healthy resource, which spends no allowance.
    - `started_at` string, date-time, required: When it began: the moment that counts for the rolling allowance.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)