A time-limited pass access window ended and its holders were removed.
When this fires
A scheduled access window reached its end time. Everyone who held it has been removed from the plan's resources on the connector. For a single-window pass that also ends the purchase: one purchase buys one window, so there is no next window to roll into. For a Pass Series holder only this date's access is stripped; the subscription ends only when the window that closed was the last date they held.
This also fires for a window that never opened because the worker was unavailable for its entire span. Such a window is closed rather than opened late, so nobody is admitted to a window that has already finished.
Caveats
- Timestamps are UTC; convert to the plan's schedule timezone before showing them.
- A subscription that this close ends also emits subscription.expired, and member.churned when it was the subscriber's last active subscription. A series holder mid-slate emits neither, only pass_series.leg_completed. De-duplicate if you consume several of these.
- A cancelled window does not emit this event. It emits pass.window_cancelled instead, with per-holder detail in pass.holder_moved and pass.holder_stranded.
Related events
- pass.window_opened: paired transition.
- member.resource_removed: per-subscriber revocation.
Headers
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
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.