sequence.* events

A recovery sequence changed.

When this fires

A creator renamed the sequence, moved it to another trigger, switched it on or off, or added, rewrote or removed a step on the Revenue Recovery page. Every save fires it, so a consumer always holds the snapshot after the latest write. Switching a sequence off also lets every member part-way through it go, each as sequence.exited with the reason disabled, and enrols nobody new until it runs again.

Caveats

  • Positions move, enrolments do not. A member who was due the removed step receives the step that took its place, and a member past the last remaining step completes on the next sweep. Read the steps by id if you track one.
  • A sequence may hold up to 8 steps. The ninth is refused on the dashboard and fires nothing.

Related events

  • sequence.created: the sequence was built.
  • sequence.exited: the members let go when the sequence was switched off.
  • sequence.deleted: the sequence was deleted.
postWebhooksequence.updated

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.updated' required

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