coupon.created
A new coupon code was authored in a project.
When this fires
A creator authored a new coupon code over the REST API or via the create_coupon MCP tool. Coupons authored in the dashboard or through the bot do not currently emit this event; those surfaces write through the service layer directly.
It fires on authoring, not on availability. A coupon created with a future starts_at fires this immediately and only becomes redeemable later, so do not read this as "a discount is now live": check starts_at and active.
There is no separate event for a coupon becoming redeemable when its
starts_atpasses. Schedule againststarts_atfrom this payload if you need that moment.
Caveats
- The snapshot carries no redemption counts and no plan restriction. Counts move independently of the coupon row, and the plan list is a separate relation. Read both from the coupon endpoint if you need them.
- A coupon can be created already switched off.
active: falsehere is legitimate, not a race: a creator can author a code ahead of a campaign and switch it on later, which emitscoupon.activated. codeis uppercase regardless of what was typed. A creator enteringblackfridaygetsBLACKFRIDAY. Compare case-sensitively against the uppercase form.- Timestamps inside
data.couponare ISO 8601 with offset (+00:00), unlike the envelope'screated_at, which usesZ. Both are UTC.
Related events
coupon.updated: the same snapshot after a change, plus a list of what moved.coupon.activated/coupon.deactivated: availability flips.coupon.redeemed: a subscriber actually used it.
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