A time-limited pass access window opened and its holders were admitted.
When this fires
A scheduled access window on a time-limited pass plan reached its start time. Everyone holding that window has been admitted to the plan's resources on the connector.
Windows are processed every minute, so this fires within roughly 60 seconds of the advertised start time rather than exactly on it.
This describes the window, not an individual subscriber. For per-member grants, subscribe to member.resource_added, which fires once per subscriber per resource.
Caveats
- Timestamps are UTC. A pass schedule is authored in the creator's timezone, so rendering these without converting will show the wrong local time to buyers.
- subscribers_affected counts holders who were eligible at open time, not at purchase time. Cancelled and paused passes are excluded, so this can be lower than the number sold.
- Anyone who buys after this fires is outside the count entirely; a plan whose sales cutoff is anchored to the window end keeps selling while the window runs. Those admissions arrive as member.resource_added, not as a second pass.window_opened.
- A window whose worker was down for its entire span is closed without ever opening. In that case this event never fires and only pass.window_closed is emitted.
Related events
- pass.window_closed: paired transition.
- member.resource_added: per-subscriber grant.
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.