sequence.* events

A member left a recovery sequence before its last step.

When this fires

A passage ended for a reason other than the member paying again: the creator switched the sequence off (disabled) or deleted it (deleted), or the member could not be reached on any connected account and the platform refused for good (opted_out). It fires once per passage. A passage that ran through every step completes without an event, and one that ended because the member paid again fires sequence.converted instead.

Related events

  • sequence.updated: the switch-off behind a disabled exit.
  • sequence.deleted: the deletion behind a deleted exit.
  • sequence.converted: the one ending that is not an exit.
postWebhooksequence.exited

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'sequence.exited' required

The event name, always sequence.exited 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.