coupon.* events

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: true is one of four conditions. A coupon still will not apply if it is outside its starts_at / expires_at window, 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_at simply arrived does not emit this; nothing changed on the row. If you need the moment a code becomes redeemable, schedule against starts_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.
postWebhookcoupon.activated

Headers

SB-Signaturestring required

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=.

SB-Event-Idstring required

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.

SB-Event-Namestring required

The event name, the same as the envelope's type.

Content-Typestring required

Always application/json.

User-Agentstring required

Always Subscriby-Webhooks/1.0.

Payload

idstring required

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type'coupon.activated' required

The event name, always coupon.activated here.

created_atstring date-time required

When the event was emitted, server time, ISO 8601.

api_versionstring required

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_idstring uuid nullable required

The project the event belongs to; null for team-scoped and billing events.

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.