---
title: "A new access window came into existence on a time-limited pass plan."
method: POST
path: "pass.window_scheduled"
tags: ["pass.* events"]
---

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

`POST pass.window_scheduled` (webhook)

### 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](https://docs.subscriby.net/api/v1/reference/pass-windows).

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](https://docs.subscriby.net/creators/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.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, 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_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `plan_id` string, uuid, required: The pass plan the window belongs to.
    - `window_id` string, uuid, required: The window that was created. This is the id a Pass Series points at.
    - `starts_at` string, date-time, required: Window start, **always UTC**.
    - `ends_at` string, date-time, required: Window end, always UTC.
    - `timezone` string, nullable, required: The IANA zone the schedule was authored in. Render `starts_at`/`ends_at` in this, not UTC. `null` when the plan has no timezone recorded; fall back to UTC.
    - `source` 'generated' | 'manual', required: `generated` (built from the plan's recurrence) or `manual` (placed by hand).

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: 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.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)