pass_series.seats_exhausted

When this fires

A purchase took the last seat on a series with a Seat Limit. The season is now sold out: its portal card reads Sold out, but a checkout already in flight is not blocked; the seat cap is only claimed once the payment lands, so a late buyer can pay, be given nothing, and be told to ask the organiser for a refund. Treat this event as the cue to stop promoting the season yourself.

Fires at the transition, once. An endpoint told this on every subsequent read would be told a fact rather than an event.

Caveats

• Sold out is not permanent. A seat is released when a holder cancels or is refunded, and the series goes back on sale, at which point a later purchase can exhaust it again and emit this a second time. Treat it as a state change, not a terminal state.
• Only holders who actually hold the series consume a seat. A checkout that was started and abandoned, or a payment that never cleared, does not.
• A series with no Seat Limit never emits this at all.
• Raising the cap does not emit anything. If you are tracking availability, read seats_remaining on the plan rather than inferring it from this event alone.

Related events

• pass_series.purchased: every purchase, each carrying seats_remaining.
• plan.deactivated: the series coming off sale for good once its dates have run.

Header Parameters

The signed JSON envelope posted to your endpoint.

Response Body