---
title: "A creator cancelled a time-limited pass access window, and its holders were resettled."
method: POST
path: "pass.window_cancelled"
tags: ["pass.* events"]
---

# A creator cancelled a time-limited pass access window, and its holders were resettled.

`POST pass.window_cancelled` (webhook)

### When this fires

A creator cancelled a scheduled access window from **Manage Access Windows** or [the cancel endpoint](https://docs.subscriby.net/api/v1/reference/pass-windows): a postponed match, a called-off session. This is never automatic: regeneration, slot edits and plan changes all leave sold windows alone, so cancelling is always a deliberate act.

By the time this fires every holder has already been resettled. Each one was either moved to the next available window on the same plan, or, when nothing suitable was left, had their pass ended and was told to ask the creator for a refund. The tallies are in the payload, and the per-holder detail arrives as `pass.holder_moved` and `pass.holder_stranded` for ordinary passes, or `pass_series.leg_substituted` and `pass_series.leg_dropped` for season-ticket holders.

> Cancelling cannot be undone. The window keeps its start time permanently, so the same instant can never be re-created on that plan: schedule regeneration skips it and adding it by hand is refused.

### Caveats

- Timestamps are UTC; convert to the plan's schedule timezone before showing them.
- **The counts exclude holders who were paused, past due, or had already cancelled their own pass.** Those are left bound to the cancelled window and are not resettled or messaged, so reconciling refunds from `refund_due` alone will miss them. They also exclude season-ticket holders who lost this one date: those are resettled and messaged, and emit `pass_series.leg_dropped`, but are counted in neither `rebound`, `refund_due`, nor `subscribers_affected`.
- `refund_due` is a count, not a list. Consume `pass.holder_stranded` for the identities and amounts; nothing in the dashboard records them durably.
- No refund is issued by Subscriby. The buyer is told to contact the creator.
- Cancelling a window that is already **Open** evicts its holders immediately: anyone already admitted is removed from the connector's resources and their invite links stop working within seconds. They are not charged again and receive fresh links automatically when their replacement window opens.
- A cancelled window never emits `pass.window_closed`.

### Related events

- `pass.holder_moved`: one per resettled holder.
- `pass.holder_stranded`: one per holder owed a refund.

## 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_cancelled', required: The event name, always `pass.window_cancelled` 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 belonged to.
    - `window_id` string, uuid, required: The access window that was cancelled.
    - `starts_at` string, date-time, required: Window start, **always UTC**.
    - `ends_at` string, date-time, required: Window end, always UTC.
    - `rebound` integer, required: Holders moved to another window on the same plan.
    - `refund_due` integer, required: Holders whose pass ended because nothing was available. **These are owed money.**
    - `subscribers_affected` integer, required: `rebound + refund_due`.

## 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)