recovery.* events

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

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.
postWebhookrecovery.standby_registered

Headers

SB-Signaturestring required

t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.

SB-Event-Idstring required

The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.

SB-Event-Namestring required

The event name, the same as the envelope's type.

Content-Typestring required

Always application/json.

User-Agentstring required

Always Subscriby-Webhooks/1.0.

Payload

idstring 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_atstring date-time required

When the event was emitted, server time, ISO 8601.

api_versionstring required

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_idstring uuid nullable required

The project the event belongs to; null for team-scoped and billing events.

Response

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

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.