One step of a recovery sequence reached a member.
When this fires
The hourly sweep found the step due and the member's connected account took the message: the creator's text with the placeholders filled for this member, the way back to the project as a button, and the step's coupon code in the text where the creator placed it. The message goes out as an announcement, so the member's channel choices and opt-outs apply. A platform that refuses for the moment (a rate limit, a passing fault, a misconfigured installation) fires nothing and the step stays due for the next hour; one that refuses for good, or a member with no account to reach, fires nothing and ends the passage as sequence.exited with the reason opted_out. After the last step the passage completes quietly: no event marks completion.
Related events
- sequence.enrolled: the passage this step belongs to.
- sequence.converted: the member paid again after reading it.
- coupon.redeemed: the step's coupon used at checkout.
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.