---
title: "A standby is no longer kept: the creator removed it, registered another in its place, or a recovery consumed it."
method: POST
path: "recovery.standby_removed"
tags: ["recovery.* events"]
---

# A standby is no longer kept: the creator removed it, registered another in its place, or a recovery consumed it.

`POST recovery.standby_removed` (webhook)

### When this fires

A standby bot or standby chat leaves the reserve. `reason` says why: `removed` when the creator took it away, `replaced` when a new standby bot took the slot, `used` when a recovery consumed it (a bot relink from the standby, a one-click Swap & Grant onto the standby chat, or an automatic failover).

### Caveats

- A standby consumed by a recovery fires this beside the recovery's own events (`recovery.resource_failed_over` or `recovery.resource_replaced`, or the bot recovery's `recovery.operation_completed`); use `reason: used` to tell it from a deliberate removal.
- The readiness checklist counts standbys, so a `removed` or `used` standby lowers the score until a new one is registered.

### Related events

- `recovery.standby_registered`: the standby being kept.

## 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_removed', required: The event name, always `recovery.standby_removed` 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 covered; null for a standby bot.
    - `connector` string, nullable, required: The connector the standby lived on.
    - `reason` 'removed' | 'replaced' | 'used', required: Why the standby left the reserve.

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