pass.window_cancelled
A creator cancelled a time-limited pass access window, and its holders were resettled.
When this fires
A creator cancelled a scheduled access window from Manage Access Windows or the cancel endpoint: a postponed match, a called-off session. This is never automatic: regeneration, slot edits and plan changes all leave sold windows alone, so cancelling is always a deliberate act.
By the time this fires every holder has already been resettled. Each one was either moved to the next available window on the same plan, or, when nothing suitable was left, had their pass ended and was told to ask the creator for a refund. The tallies are in the payload, and the per-holder detail arrives as pass.holder_moved and pass.holder_stranded for ordinary passes, or pass_series.leg_substituted and pass_series.leg_dropped for season-ticket holders.
Cancelling cannot be undone. The window keeps its start time permanently, so the same instant can never be re-created on that plan: schedule regeneration skips it and adding it by hand is refused.
Caveats
- Timestamps are UTC; convert to the plan's schedule timezone before showing them.
- The counts exclude holders who were paused, past due, or had already cancelled their own pass. Those are left bound to the cancelled window and are not resettled or messaged, so reconciling refunds from
refund_duealone will miss them. They also exclude season-ticket holders who lost this one date: those are resettled and messaged, and emitpass_series.leg_dropped, but are counted in neitherrebound,refund_due, norsubscribers_affected. refund_dueis a count, not a list. Consumepass.holder_strandedfor the identities and amounts; nothing in the dashboard records them durably.- No refund is issued by Subscriby. The buyer is told to contact the creator.
- Cancelling a window that is already Open evicts its holders immediately: anyone already admitted is removed from the connector's resources and their invite links stop working within seconds. They are not charged again and receive fresh links automatically when their replacement window opens.
- A cancelled window never emits
pass.window_closed.
Related events
pass.holder_moved: one per resettled holder.pass.holder_stranded: one per holder owed a refund.
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