pass.* events

A new access window came into existence on a time-limited pass plan.

When this fires

A dated access window was created on a pass plan: either generated from the plan's recurrence, or placed by hand from Manage Access Windows or the pass windows endpoint.

This is the event that lets you mirror a schedule outward without polling for it. Every other pass.* event describes something happening to a window that already exists; this one is the window arriving.

Why this matters more once a series is involved. A Pass Series can be set to absorb new windows automatically as they are scheduled, and its holders are granted them at no charge. Without this event an integration has no way to learn a season grew except by re-reading the plan: the difference between a synced calendar and a stale one.

Caveats

  • Editing a schedule regenerates windows in bulk. Saving a pass plan rebuilds its unsold future windows, so a single edit can emit this many times in quick succession. Batch on your side rather than treating each as an isolated announcement.
  • Regeneration never touches a window somebody bought, a window a series points at, or one a creator pinned, so those are not deleted and re-created, and do not re-emit.
  • source: manual windows are never rebuilt by a schedule edit. They fire this once, when placed.
  • Timestamps are UTC. timezone is on the payload precisely so you do not have to look the plan up to render them correctly.

Related events

  • pass.window_opened: the same window reaching its start time.
  • pass.window_cancelled: a window being withdrawn.
  • pass_series.leg_added: a rule absorbing a newly-scheduled window into a live season.
postWebhookpass.window_scheduled

Headers

SB-Signaturestring required

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=.

SB-Event-Idstring required

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.

SB-Event-Namestring required

The event name, the same as the envelope's type.

Content-Typestring required

Always application/json.

User-Agentstring required

Always Subscriby-Webhooks/1.0.

Payload

idstring required

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type'pass.window_scheduled' required

The event name, always pass.window_scheduled here.

created_atstring date-time required

When the event was emitted, server time, ISO 8601.

api_versionstring required

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_idstring uuid nullable required

The project the event belongs to; null for team-scoped and billing events.

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.