Pass Roster API

The Pass Roster is a project's members against the dates its pass plans sell: who holds which date, where each of them stands on it, and who was moved from where when a date was cancelled. It is the dashboard's Pass Roster page as a page of rows, read the same way the page reads it, so a spreadsheet, a CRM or an agent answers "who is on Saturday, and who was rolled over from Thursday" without opening every plan.

The rows are members; the columns are dates. Every date that touches the span is a column, cancelled ones included, because a cancelled date is where the departures off it are read; a date beyond the span that holders were moved onto is listed beside the columns, so a departure always names a date the client can read. The moves come from the project's pass move log, which keeps every hop a pass made, rather than from the ledger, which keeps only the last.

EndpointsCopy Anchor Link

Related

Pass Windows APIThe dates themselves, with whether each is on sale and how many hold it.Subscriptions APIOne purchase's own trail of moves, GET /v1/subscriptions/{subscription}/pass-moves.Members APIThe member each row prints, and the ability the roster reads under.Pass RosterThe page, its seven words and its dialogs.pass.* eventspass.holder_moved fires for every hop, with its reason and move_id.