---
title: "A line of the Disaster Recovery readiness checklist changed state, and here is the whole checklist as it stands now."
method: POST
path: "recovery.readiness_changed"
tags: ["recovery.* events"]
---

# A line of the Disaster Recovery readiness checklist changed state, and here is the whole checklist as it stands now.

`POST recovery.readiness_changed` (webhook)

### When this fires

The readiness checklist is what a creator has in place before anything happens: a second factor on the account, a backup sign-in account, and, per connector, the standbys, mirrors and automatic failover the platform can verify. Subscriby records the checklist's state after every event that could move a line (a standby registered or removed, a resource failed over or replaced, an account relinked, a connector installed, connected, disconnected or uninstalled) and once a night for the things that fire no event (a second factor, a passkey, a plan change). When the state differs from the last one recorded, this event fires with the checklist as it stands. Recording the same state twice fires nothing. Readiness is the creator's, not one project's, so the envelope `project_id` is null.

### Caveats

- The first checklist ever recorded for a creator fires nothing: there is no earlier state to differ from.
- Reminders (a copy of the content elsewhere, a second human administrator) never appear here; they cannot be verified.
- The labels, descriptions and fix links of each line are not in the payload; read them from [the readiness endpoint](https://docs.subscriby.net/api/v1/reference/disaster-recovery).

### Related events

- `recovery.standby_registered`: one of the changes that leads here.
- `recovery.standby_removed`: another.

## 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.readiness_changed', required: The event name, always `recovery.readiness_changed` 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.
    - `completed` integer, required: Verifiable lines in place.
    - `total` integer, required: Verifiable lines in all; reminders are not counted.
    - `complete` boolean, required: Whether every verifiable line is in place.
    - `items` object[], required: Every verifiable line, in the order the dashboard shows them.
      - `key` string, required: The line's key: `second_factor`, `backup_identity`, or a connector's own key such as `standby_spaces`.
      - `connector` string, nullable, required: The connector the line belongs to; `null` for the account-level lines.
      - `done` boolean, required: Whether the line is in place.
      - `locked` boolean, required: Whether the plan lacks the prevention feature the line needs.
    - `changed` string[], required: The lines still open after the change, as `connector:key` (or `key` for an account-level line).

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