pass_series.purchased
Someone bought a season ticket and their whole slate was issued.
When this fires
A Pass Series was bought, or comped with an access code, and every date on the slate has been written into the buyer's ledger. They hold all of them from this moment; there is nothing further to claim.
This fires in addition to
subscription.activated. A series is a subscription row, so a purchase emits both. An endpoint subscribed to the two receives two deliveries for one purchase and must de-duplicate onsubscription_id. That is not a quirk to work around:subscription.activatedis what you want for revenue, and this is what you want for the slate. They answer different questions about the same event.
Caveats
passes_granted + passes_already_held = passes_total. Buying a date you already own is allowed on purpose; it is de-duplicated at grant time rather than refused, and the buyer is told so on their timeline. A non-zeropasses_already_heldis normal, not an error.passes_totalcounts what this buyer received, which on a mid-season purchase is fewer than the slate holds: dates that have already run are never issued. Read the plan if you need the full slate length.- The span is the series', not this buyer's.
starts_atandends_atare the plan's cached slate span, so on a mid-season purchasestarts_atcan precede every date the buyer actually holds. Only thepasses_*counts are buyer-scoped. - A series absorbing new dates later does not re-emit this. That is
pass_series.leg_added.
Related events
subscription.activated: the same purchase as revenue. De-duplicate onsubscription_id.pass_series.leg_completed: one date of this slate finishing.pass_series.completed: the final date finishing.pass_series.seats_exhausted: when a purchase takes the last seat.
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