Pass Windows API

A pass window is one dated stretch of access on a kind: pass plan: the Saturday 09:00–12:00 a buyer of a match-day pass actually gets.

A pass window is one dated stretch of access on a kind: pass plan: the Saturday 09:00–12:00 a buyer of a match-day pass actually gets. Most windows are generated from the plan's slots; a creator can also place one by hand. A pass series is a slate of these windows, so their ids are what a series points at.

Windows are their own resource rather than an include on the plan: an integration authoring a series needs the ids without pulling a whole plan per source plan. The writes are the three the dashboard's Manage Access Windows panel offers (place a date, cancel one, nudge its holders) and they run the same actions the panel does.

Endpoints

GET/v1/projects/{project}/pass-windowsList a project's pass windows GET/v1/projects/{project}/pass-windows/{window}Get a pass window POST/v1/projects/{project}/plans/{plan}/pass-windowsPlace a pass window by hand POST/v1/projects/{project}/pass-windows/{window}/cancelCancel a pass window POST/v1/projects/{project}/pass-windows/{window}/remindRemind a window's holders

List a project's pass windows

GET

curl "https://api.subscriby.net/v1/projects/$PROJECT_ID/pass-windows?status=scheduled&sellable_only=true" \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

The project's windows across every pass plan, soonest first, 50 per page (per_page 1 to 100; limit is accepted as an alias). Filters are validated before they reach the query: an unknown status or a malformed date is a 422 VALIDATION_FAILED naming the field, not an empty page.

The list also opens to project-subscription-plan:view-any. The list shipped under the plan ability before the pass-window:* family had any surface, and it is what the n8n node and the MCP tool docs named. A token holding only project-subscription-plan:view-any therefore still satisfies the pass-window:view-any gate. Mint new tokens with the precise ability; the alias exists so old ones keep working.

Requires ability

pass-window:view-any

The token must hold this ability, or the call is refused with 403.

MCP tool

list_pass_windows

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken

AuthorizationBearer <token>

A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

Query Parameters

plan_id?|

One pass plan of the project only.

Formatuuid

status?|

One state only: scheduled, open, closed or canceled. Anything else is refused.

from?|

Only windows starting at or after this moment, ISO 8601.

Formatdate-time

to?|

Only windows starting at or before this moment, ISO 8601.

Formatdate-time

sellable_only?boolean

Keep only windows a buyer could still purchase.

page?integer

The 1-based page to return. A page past the last answers an empty data array with meta.total still filled, so a loop can stop without guessing.

Range1 <= value

Default1

per_page?integer

Rows per page, 1 to 100. A higher value clamps to the cap silently. Defaults to 50.

Range1 <= value <= 100

Default50

sort_by?string

The column to order by. Defaults to created_at; a column the endpoint does not offer falls back to the default rather than failing.

Default"created_at"

sort_direction?string

asc or desc. Defaults to desc.

Default"desc"

Value in

"asc"
"desc"

limit?integer

Legacy alias of per_page, kept for clients that predate it. per_page wins when both are sent.

Range1 <= value <= 100

Responses

200OKapplication/json

The page, soonest first.

data*array<>

The items on this page.

links*

Links to the first, last, previous and next pages.

meta*

The paging counters for this page.

401UnauthorizedAUTHENTICATION_REQUIREDapplication/json

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers FORBIDDEN, TEAM_TIER_REQUIRED or CONNECTOR_TIER_REQUIRED with the same status, and says so in its own description.

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

An id in the path names nothing the token can see. TENANT_MISMATCH: the project sits outside the token's scope:project: allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.

error*

The one envelope every failure uses.

422Validation failedVALIDATION_FAILEDapplication/json

error*

The one envelope every failure uses.

429Too many requestsRATE_LIMITEDapplication/json

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/pass-windows"

{  "data": [    {      "id": "3d5a8c72-b016-4e94-8fa7-61c209d4e738",      "plan_id": "c4e82f16-93a7-4d5b-b81c-6e0f27a94d3b",      "plan_name": "Match Day Pass",      "starts_at": "2026-09-20T13:00:00+00:00",      "ends_at": "2026-09-20T16:00:00+00:00",      "timezone": "America/New_York",      "local_range": "Sun 20 Sep 2026, 09:00 – 12:00 EDT",      "duration_minutes": 180,      "status": "scheduled",      "source": "generated",      "sellable": true,      "holders": 38    }  ],  "links": {    "first": "string",    "last": "string",    "prev": "string",    "next": "string"  },  "meta": {    "current_page": 1,    "from": 1,    "last_page": 1,    "links": [      {        "url": "string",        "label": "string",        "active": true      }    ],    "path": "string",    "per_page": 0,    "to": 1,    "total": 0  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: PassWindowResource[];  links: Links;  meta: Meta;}export interface PassWindowResource {  id: string;  plan_id: string;  plan_name: string;  starts_at: string;  ends_at: string;  timezone: string | null;  local_range: string;  duration_minutes: number;  status: string;  source: string;  sellable: boolean;  holders: number;}export interface Links {  first: string | null;  last: string | null;  prev: string | null;  next: string | null;}export interface Meta {  current_page: number;  from: number | null;  last_page: number;  links: Link[];  path: string | null;  per_page: number;  to: number | null;  total: number;}export interface Link {  url: string | null;  label: string;  active: boolean;}

Get a pass window

GET

One window, with sellable and holders resolved for it. A window is resolved within the project: a window id that belongs to another project, another team, or to nothing at all is a 404 RESOURCE_NOT_FOUND, so an id's existence never leaks.

Field	Type	Notes
`starts_at`	string	ISO 8601, UTC. Store this.
`ends_at`	string	ISO 8601, UTC.
`timezone`	string	The IANA zone the plan's schedule was authored in. Render window times in this, never in UTC.
`local_range`	string	The same window as a person reads it, already in `timezone`: what the dashboard, the portal and the bot all print.
`duration_minutes`	integer	Derived from the two instants.
`status`	string	`scheduled`, `open`, `closed` or `canceled`. Set by the scheduler as the window's start and end pass; `canceled` only by an explicit cancel.
`source`	string	`generated` from the plan's slots, or `manual` when placed by hand. Manual windows survive a schedule rebuild; generated ones are regenerated.
`sellable`	boolean	Whether a buyer could purchase this window right now: the plan's sales cutoff, resolved for the whole page in one query rather than per row.
`holders`	integer	How many purchases currently hold the window.

Why both UTC and a local range. A pass schedule is authored in the creator's zone and rendered in it everywhere else in the product. Returning only UTC would leave every consumer converting, and getting it wrong across a daylight-saving boundary. starts_at is for storing and comparing; local_range is for showing.

Requires ability

pass-window:view

The token must hold this ability, or the call is refused with 403.

MCP tool

get_pass_window

Runs the same action from an agent, behind the same ability.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

window*string

The window, resolved within the project with its holder count and sale flag.

Formatuuid

Responses

200OKapplication/json

The window.

data*

The response's payload.

401UnauthorizedAUTHENTICATION_REQUIREDapplication/json

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

429Too many requestsRATE_LIMITEDapplication/json

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/pass-windows/497f6eca-6276-4993-bfeb-53cbbbba6f08"

{  "data": {    "id": "3d5a8c72-b016-4e94-8fa7-61c209d4e738",    "plan_id": "c4e82f16-93a7-4d5b-b81c-6e0f27a94d3b",    "plan_name": "Match Day Pass",    "starts_at": "2026-09-20T13:00:00+00:00",    "ends_at": "2026-09-20T16:00:00+00:00",    "timezone": "America/New_York",    "local_range": "Sun 20 Sep 2026, 09:00 – 12:00 EDT",    "duration_minutes": 180,    "status": "scheduled",    "source": "generated",    "sellable": true,    "holders": 38  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: PassWindowResource;}export interface PassWindowResource {  id: string;  plan_id: string;  plan_name: string;  starts_at: string;  ends_at: string;  timezone: string | null;  local_range: string;  duration_minutes: number;  status: string;  source: string;  sellable: boolean;  holders: number;}

Place a pass window by hand

POST

Places a window by hand on a kind: pass plan. This is how schedule_mode: fixed gets its dates, and how a repeating plan gets the one-off that does not fit its pattern.

curl -X POST https://api.subscriby.net/v1/projects/$PROJECT_ID/plans/$PLAN_ID/pass-windows \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \  -H "Idempotency-Key: $(uuidgen)" \  -H "Content-Type: application/json" \  -d '{    "starts_at": "2026-09-20 09:00",    "duration_minutes": 180  }'

Answers 201 with the new window: status: scheduled, source: manual, holders: 0. The request above and "starts_at": "2026-09-20T09:00:00-04:00" describe the same instant for a plan in America/New_York, and both come back as "2026-09-20T13:00:00+00:00". Raises pass.window_scheduled with source: manual.

A manual window is never touched by regeneration: editing pass.slots on the plan rebuilds the generated windows and leaves this one where you put it. Every pass series with a rule is asked to look at the new date afterwards, so a matching series absorbs it as described on the Plans page.

Each refusal below is a 422 VALIDATION_FAILED naming the field, the same wording the dashboard's panel shows.

Requires ability

pass-window:create

The token must hold this ability, or the call is refused with 403.

Fires one event

pass.window_scheduled

Delivered to every endpoint subscribed to it once the change is made.

MCP tool

create_pass_window

Runs the same action from an agent, behind the same ability.

Idempotent

Idempotency-Key

Send the header on every call; the same key replays the original response for 24 hours.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

plan*string

The plan, resolved within the project.

Formatuuid

Header Parameters

Idempotency-Key*string

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Formatuuid

Request body

JSONWhat the request carriesRequiredapplication/json

A window to place by hand on a time-limited pass plan: when it starts and how long it lasts.

starts_at*string

When access opens, ISO 8601. A value with no offset is read as wall-clock time in the plan's timezone, exactly as the dashboard authors it; a value with an offset or Z is the instant it names. Must be in the future, judged in the plan's own zone.

Formatdate-time

duration_minutes*integer

How long the window lasts, a whole number of minutes, at least 1. The plan's configured floor and ceiling apply: 5 minutes and 30 days by default.

Range1 <= value

Responses

201Createdapplication/json

The window.

data*

The response's payload.

400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

error*

The one envelope every failure uses.

401UnauthorizedAUTHENTICATION_REQUIREDapplication/json

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json

The key was already used in the last 24 hours with a different request body.

error*

The one envelope every failure uses.

422Validation failedVALIDATION_FAILEDapplication/json

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when the plan is not a time-limited pass: a subscription or a series has no windows of its own. VALIDATION_FAILED: when the start is in the past, judged in the plan's own zone. VALIDATION_FAILED: when the length is under the plan's floor or over its ceiling (5 minutes and 30 days by default). VALIDATION_FAILED: when the plan already has a window starting at that instant. VALIDATION_FAILED: when the plan stops selling a fixed number of minutes before a window **ends** and the window is not longer than that cutoff, so it would never be on sale while it runs.

error*

The one envelope every failure uses.

425Too earlyIDEMPOTENCY_REPLAY_IN_PROGRESSapplication/json

The first request with this key is still running; retry in a few seconds and the original response is replayed.

error*

The one envelope every failure uses.

429Too many requestsRATE_LIMITEDapplication/json

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X POST "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/plans/497f6eca-6276-4993-bfeb-53cbbbba6f08/pass-windows" \  -H "Idempotency-Key: 0199a4ae-6c02-7b5c-9f51-c5f0da5e2f12" \  -H "Content-Type: application/json" \  -d '{    "starts_at": "2019-08-24T14:15:22Z",    "duration_minutes": 1  }'

{  "data": {    "id": "9c1f4e27-5a8b-4d63-b2e0-8f7a6c5d4e31",    "plan_id": "c4e82f16-93a7-4d5b-b81c-6e0f27a94d3b",    "plan_name": "Match Day Pass",    "starts_at": "2026-09-20T13:00:00+00:00",    "ends_at": "2026-09-20T16:00:00+00:00",    "timezone": "America/New_York",    "local_range": "Sun 20 Sep 2026, 09:00 – 12:00 EDT",    "duration_minutes": 180,    "status": "scheduled",    "source": "manual",    "sellable": true,    "holders": 0  }}

Type definitions

The shapes above as types, ready to paste into your client.

Request

export interface StorePassWindowRequest {  starts_at: string;  duration_minutes: number;}

Response

export interface Response {  data: PassWindowResource;}export interface PassWindowResource {  id: string;  plan_id: string;  plan_name: string;  starts_at: string;  ends_at: string;  timezone: string | null;  local_range: string;  duration_minutes: number;  status: string;  source: string;  sellable: boolean;  holders: number;}

Cancel a pass window

POST

curl -X POST https://api.subscriby.net/v1/projects/$PROJECT_ID/pass-windows/$WINDOW_ID/cancel \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \  -H "Idempotency-Key: $(uuidgen)"

By the time the response arrives every holder has been resettled, and meta says how:

Tally	What happened to those holders
`rebound`	Moved to the plan's next window on sale, and told so. Their invite links are re-issued when the new window opens.
`refund_due`	The schedule had nothing left to offer, so their pass was ended and they were told to ask the creator for a refund.
`legs_dropped`	Season-ticket holders who lost this one date and keep the rest of their series. Their message states what the date was worth of what they paid.

Subscriby never moves the refunds. refund_due and legs_dropped are statements, not actions. The money stays where it is until the creator refunds it at the gateway. An integration that wants to act on them should subscribe to pass.holder_stranded and pass_series.leg_dropped, which carry the amount per holder.

Cancelling is a POST verb and not a DELETE on purpose: it resettles every holder, moving them on or ending their pass, which is far too consequential to read as removing a row. It also cannot be undone: the window keeps its start permanently, so the same instant can never be re-created on that plan.

Raises pass.window_cancelled carrying the tallies, plus one event per holder: pass.holder_moved or pass.holder_stranded for ordinary passes, pass_series.leg_substituted or pass_series.leg_dropped for season-ticket holders. A window that is already cancelled is answered 200 with every tally at zero, so a retry after a lost response changes nothing.

Requires ability

pass-window:delete

The token must hold this ability, or the call is refused with 403.

Fires events

pass.window_cancelled pass.holder_moved pass.holder_stranded pass_series.leg_substituted pass_series.leg_dropped

Delivered to every endpoint subscribed to them once the change is made.

MCP tool

cancel_pass_window

Runs the same action from an agent, behind the same ability.

Idempotent

Idempotency-Key

Send the header on every call; the same key replays the original response for 24 hours.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

window*string

The window, resolved within the project.

Formatuuid

Header Parameters

Idempotency-Key*string

Formatuuid

Responses

200OKapplication/json

The window, cancelled, with meta.rebound, meta.refund_due and meta.legs_dropped.

data*

The response's payload.

meta*

How every holder was resettled, as three tallies; all zero when the window was already cancelled.

400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

error*

The one envelope every failure uses.

401UnauthorizedAUTHENTICATION_REQUIREDapplication/json

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json

The key was already used in the last 24 hours with a different request body.

error*

The one envelope every failure uses.

425Too earlyIDEMPOTENCY_REPLAY_IN_PROGRESSapplication/json

The first request with this key is still running; retry in a few seconds and the original response is replayed.

error*

The one envelope every failure uses.

429Too many requestsRATE_LIMITEDapplication/json

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X POST "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/pass-windows/497f6eca-6276-4993-bfeb-53cbbbba6f08/cancel" \  -H "Idempotency-Key: 0199a4ae-6c02-7b5c-9f51-c5f0da5e2f12"

{  "data": {    "id": "3d5a8c72-b016-4e94-8fa7-61c209d4e738",    "plan_id": "c4e82f16-93a7-4d5b-b81c-6e0f27a94d3b",    "plan_name": "Match Day Pass",    "starts_at": "2026-09-20T13:00:00+00:00",    "ends_at": "2026-09-20T16:00:00+00:00",    "timezone": "America/New_York",    "local_range": "Sun 20 Sep 2026, 09:00 – 12:00 EDT",    "duration_minutes": 180,    "status": "canceled",    "source": "generated",    "sellable": false,    "holders": 0  },  "meta": {    "rebound": 38,    "refund_due": 3,    "legs_dropped": 4  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: PassWindowResource;  meta: Meta;}export interface PassWindowResource {  id: string;  plan_id: string;  plan_name: string;  starts_at: string;  ends_at: string;  timezone: string | null;  local_range: string;  duration_minutes: number;  status: string;  source: string;  sellable: boolean;  holders: number;}export interface Meta {  rebound: number;  refund_due: number;  legs_dropped: number;}

Remind a window's holders

POST

Nudges everyone who bought the window but has not yet joined, re-attaching their invite links. It is the panel's Send Reminder button; the automatic reminders a day and an hour before a window opens still run regardless.

curl -X POST https://api.subscriby.net/v1/projects/$PROJECT_ID/pass-windows/$WINDOW_ID/remind \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \  -H "Idempotency-Key: $(uuidgen)"

reminded is how many holders the connector accepted a message for, not how many were attempted: a holder who has blocked the bot is skipped without costing the rest their nudge. A window that has ended or been cancelled reminds nobody and answers 0 rather than refusing. No event fires: the reminder is a message on the connector, not a state change.

This messages real people. Do not repeat it within the same window, and to nudge one holder rather than a whole window use the subscription remind endpoint.

Requires ability

pass-window:update

The token must hold this ability, or the call is refused with 403.

MCP tool

remind_pass_window_queue

Runs the same action from an agent, behind the same ability.

Idempotent

Idempotency-Key

Send the header on every call; the same key replays the original response for 24 hours.

Authorization

bearerToken

AuthorizationBearer <token>

In: header

Path Parameters

project*string

The project, resolved by the route binder.

Formatuuid

window*string

The window, resolved within the project.

Formatuuid

Header Parameters

Idempotency-Key*string

Formatuuid

Responses

200OKapplication/json

window_id and how many holders were reminded.

data*

The response's payload.

400Bad requestIDEMPOTENCY_KEY_MISSINGapplication/json

Every write needs an Idempotency-Key header. Send a fresh UUID per distinct operation.

error*

The one envelope every failure uses.

401UnauthorizedAUTHENTICATION_REQUIREDapplication/json

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

error*

The one envelope every failure uses.

403ForbiddenTOKEN_MISSING_ABILITYapplication/json

error*

The one envelope every failure uses.

404Not foundRESOURCE_NOT_FOUNDapplication/json

error*

The one envelope every failure uses.

409ConflictIDEMPOTENCY_KEY_REUSEDapplication/json

The key was already used in the last 24 hours with a different request body.

error*

The one envelope every failure uses.

425Too earlyIDEMPOTENCY_REPLAY_IN_PROGRESSapplication/json

The first request with this key is still running; retry in a few seconds and the original response is replayed.

error*

The one envelope every failure uses.

429Too many requestsRATE_LIMITEDapplication/json

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

error*

The one envelope every failure uses.

Call it from your code

A sample request in your language, the body each status answers with, and the types to hold them.

curl -X POST "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/pass-windows/497f6eca-6276-4993-bfeb-53cbbbba6f08/remind" \  -H "Idempotency-Key: 0199a4ae-6c02-7b5c-9f51-c5f0da5e2f12"

{  "data": {    "window_id": "3d5a8c72-b016-4e94-8fa7-61c209d4e738",    "reminded": 12  }}

Type definitions

The shapes above as types, ready to paste into your client.

export interface Response {  data: Data;}export interface Data {  window_id: string;  reminded: number;}

Plans APIThe pass and pass_series kinds these windows belong to, and the successor endpoint.Subscriptions APINudge one holder instead of a whole window.Time-Limited PassesAdding a date by hand, cancelling a window, and what holders see.pass.* eventspass.window_opened and pass.window_closed come from the scheduler as each window's start and end pass, not from any call here.

Pass Windows API

EndpointsCopy Anchor Link

List a project's pass windowsCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Query ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Get a pass windowCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Place a pass window by handCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Header ParametersCopy Anchor Link

Request bodyCopy Anchor Link

ResponsesCopy Anchor Link

Cancel a pass windowCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Header ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Remind a window's holdersCopy Anchor Link

AuthorizationCopy Anchor Link

Path ParametersCopy Anchor Link

Header ParametersCopy Anchor Link

ResponsesCopy Anchor Link

Related

On this page

Endpoints

List a project's pass windows

Authorization

Path Parameters

Query Parameters

Responses

Get a pass window

Authorization

Path Parameters

Responses

Place a pass window by hand

Authorization

Path Parameters

Header Parameters

Request body

Responses

Cancel a pass window

Authorization

Path Parameters

Header Parameters

Responses

Remind a window's holders

Authorization

Path Parameters

Header Parameters

Responses