A recovery sequence was built in a project.
When this fires
A creator built a sequence on the Revenue Recovery page: a name, a trigger and whether it runs. It fires on authoring, with no steps yet; the steps arrive one by one as sequence.updated. Nobody is enrolled by this event: enrolment waits for the trigger to fire for a member, and a sequence with no steps enrols nobody even then.
Related events
- sequence.updated: the steps arrive, and every later change.
- sequence.enrolled: the first member enters it.
Headers
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=.
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.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
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.