coupon.updated
A coupon's terms changed, with a field-by-field list of what moved.
When this fires
A creator changed a coupon's terms: its code, name, discount, caps, minimum, or window. Fires once per update through the REST API.
The dedicated activate and deactivate endpoints emit coupon.activated / coupon.deactivated rather than this event. An update that includes active is still an update, and emits coupon.updated with active in its changes, so handle active appearing in changes as well as subscribing to the flip events.
Editing terms is dashboard and API only. The bot can create, inspect, switch off and delete a coupon, but not edit its terms; a multi-field edit is a form, not a chat. Dashboard edits do not currently emit this event (the dashboard writes through the service layer directly), so this event originates from the REST API.
changes only contains keys whose value differs. A save that changed nothing sends "changes": {}; the event still fires, because the creator did press save.
Caveats
changescompares the snapshot, not the database columns. It covers exactly the keys indata.coupon, so a change to the coupon's plan restriction does not appear; that lives in a separate relation the snapshot deliberately omits. Re-read the coupon endpoint if you track which plans a code covers.fromandtokeep their original types. A decimal field gives you decimal strings, an integer field integers, a nullable fieldnull. Don't assume both sides are strings.- Changing the code does not migrate past redemptions. Redemptions already recorded stay attached to the coupon by id, so a renamed code keeps its history, but any subscriber who wrote the old string down now has a dead code.
- A change is not retroactive. Subscribers who already redeemed keep the terms they paid under; a reduced discount only affects checkouts from here on.
Related events
coupon.created: the same snapshot shape, on authoring.coupon.activated/coupon.deactivated: the on/off flip this event deliberately excludes.
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