coupon.* events

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_at passes. Schedule against starts_at from 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: false here is legitimate, not a race: a creator can author a code ahead of a campaign and switch it on later, which emits coupon.activated.
  • code is uppercase regardless of what was typed. A creator entering blackfriday gets BLACKFRIDAY. Compare case-sensitively against the uppercase form.
  • Timestamps inside data.coupon are ISO 8601 with offset (+00:00), unlike the envelope's created_at, which uses Z. 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.
postWebhookcoupon.created

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.created' required

The event name, always coupon.created 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.