coupon.activated
A coupon was switched on and is being offered at checkout again.
When this fires
A creator switched a coupon on through the activate endpoint. Flipping the switch in the dashboard or through the bot does not currently emit this event; those surfaces write through the service layer directly.
This is the availability flip, kept out of coupon.updated on purpose: an automation that cares whether a discount is live wants one event to subscribe to, not a diff of the active key on every save.
Switched on is not the same as redeemable.
active: trueis one of four conditions. A coupon still will not apply if it is outside itsstarts_at/expires_atwindow, if every use is already spoken for, or if the buyer has hit their own per-subscriber cap. Check the window and the caps in the payload before announcing a live sale.
Caveats
- This is not scheduled. It fires when a person flips the switch. A coupon whose
starts_atsimply arrived does not emit this; nothing changed on the row. If you need the moment a code becomes redeemable, schedule againststarts_at. - Re-activating a switched-off coupon does not reset its counts. Redemptions taken before it was switched off still count against
max_redemptions, so a code that was exhausted before is still exhausted after. - Idempotent flips still emit. Activating an already-active coupon over the API emits this again. De-dup on the event
id.
Related events
coupon.deactivated: the paired transition.coupon.updated: a terms change, which deliberately excludes this flip.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
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
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.
How is this guide?
Last updated on