---
title: "A pass holder was moved from a cancelled access window to the next available one on the same plan."
method: POST
path: "pass.holder_moved"
tags: ["pass.* events"]
---

# A pass holder was moved from a cancelled access window to the next available one on the same plan.

`POST pass.holder_moved` (webhook)

### When this fires

One holder of a cancelled access window was moved onto another date. Fires once per resettled holder of an ordinary pass, alongside the single `pass.window_cancelled` for the window itself. A season-ticket holder's move emits `pass_series.leg_substituted` instead; the two are mutually exclusive.

The replacement is the soonest window on the **same plan** that is still on sale, has not started yet, and that this customer does not already hold a pass for. If the schedule has nothing future left, a window already in progress is used rather than stranding them. Every window on a plan sells for the same price, which is what makes the move an even swap rather than a substitution.

They are not charged again. If the cancelled window had not opened yet, their existing invite links stay valid for the replacement date; if they had already been admitted to a live window, that access and those links are revoked immediately and fresh links are sent when the replacement window opens.

### Caveats

- Timestamps are UTC; convert to the plan's schedule timezone before showing them.
- `was_queued` is the field worth branching on. A queued holder keeps their place and is admitted automatically on the new date; an unqueued one still has to tap their link, and is sent it again as a button.
- Nobody is moved onto a date they already hold. A customer with passes for two consecutive windows skips to the one after.
- The move is written quietly, so no `subscription.*` event accompanies it. This event is the only signal.
- Holders who were paused, past due, or had cancelled their own pass are not moved and emit nothing at all.

### Related events

- `pass.window_cancelled`: the window-level event, fired once.
- `pass.holder_stranded`: the other outcome, when no window was available.

## 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.holder_moved', required: The event name, always `pass.holder_moved` 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.
    - `subscription_id` string, uuid, required: The pass purchase that moved.
    - `subscriber_id` string, uuid, required: The subscriber holding it.
    - `plan_id` string, uuid, required: The pass plan. Unchanged by the move.
    - `from_window_id` string, uuid, required: The cancelled window.
    - `from_starts_at` string, date-time, required: Cancelled window start, **always UTC**.
    - `from_ends_at` string, date-time, required: Cancelled window end, always UTC.
    - `to_window_id` string, uuid, required: The window they now hold.
    - `to_starts_at` string, date-time, required: New window start, always UTC.
    - `to_ends_at` string, date-time, required: New window end, always UTC.
    - `was_queued` boolean, required: `true` if they had already tapped their invite link, so the move asks nothing of them.

## 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/7b538e472e9a?raw)