---
title: "A spare bot is kept ready for a project, or a spare channel or group is kept ready for one resource."
method: POST
path: "recovery.standby_registered"
tags: ["recovery.* events"]
---

# A spare bot is kept ready for a project, or a spare channel or group is kept ready for one resource.

`POST recovery.standby_registered` (webhook)

### When this fires

Active Disaster Prevention keeps two kinds of standby: a **standby bot** per project (a second token, stored without a webhook and probed like any bot) and a **standby chat** per resource (a spare channel or group the bot already administers, optionally mirrored). Registering either fires this event. Registering a new standby bot where one already existed also fires `recovery.standby_removed` with `reason: replaced` for the old one.

### Caveats

- The standby's own identifiers on the platform (the bot's token, the chat's id) are never in the payload.
- Turning the mirror on or off later fires nothing; read the standby's state from the Prevention page.

### Related events

- `recovery.standby_removed`: the standby removed, replaced or used.
- `recovery.resource_failed_over`: the standby chat doing its job.

## 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.standby_registered', required: The event name, always `recovery.standby_registered` 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.
    - `standby` 'installation' | 'resource', required: `installation` for a standby bot, `resource` for a standby channel or group.
    - `project_id` string, uuid, required: The project.
    - `resource_id` string, uuid, nullable, required: The resource the standby covers; null for a standby bot.
    - `connector` string, nullable, required: The connector the standby lives on.
    - `mirror` boolean, required: Whether posts are mirrored into the standby as they are made; always false for a standby bot.

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