pass.holder_queued
A pass holder tapped their invite link and their join request is now held.
When this fires
A holder tapped their invite link for a dated window that has not opened yet. The platform holds the join request, and Subscriby records that they are queued: they will be admitted automatically the moment the window opens, whether or not they are at their phone.
This is the moment a buyer stops being a risk, and it is the one thing about a pass that a creator can still act on beforehand.
Bought is not the same as queued. A purchase and a queued request are different events with different follow-up. Someone who bought but never tapped is relying on noticing a message on the day; someone queued needs nothing at all. Everything in the product that nudges a pass holder (the reminder ladder, the creator's roll call, the manual Send Reminders button) targets the first group and skips the second.
Caveats
- This fires per join request, not per purchase. A season-ticket holder queues separately for each of their dates, so one series purchase produces at least one of these per date they tap, often spread over weeks, because the link for the next date is sent in the message that ends the previous one. A plan with more than one gated resource produces one per resource they tap, all carrying the same
window_id. - It does not fire when someone taps a link for a window that is already open. That is an immediate admission, not a queued request, and arrives as
member.resource_added. - A holder who never taps produces no event at all. Absence is the signal; see
pass.holder_missedfor the other end of that. - Re-queuing does re-emit. The handler re-stamps the queue time and fires this event again on every join request it receives, so treat
subscription_id+window_idas the idempotency key on your side.
Related events
pass.holder_missed: a holder whose window closed without them joining.pass.window_opened: the moment held requests are approved.member.resource_added: the per-resource grant that follows.
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