API Endpoints

Every endpoint, generated from the specification the API serves — request and response schemas, examples, and a playground that sends real requests.

Authenticating a request

Paste an API key into the authentication field on any operation to send real requests. Keys look like billy:o:<organization_id>:<api_key> and are sent as a Bearer token. Requests go straight from your browser to the API, and the key is never sent to this documentation site.

Events

List events

Retrieves a paginated list of events belonging to your Billy organization. Each item carries flat session summary fields; use GET /v1/events/{event_id}/sessions to enumerate the sessions of an event.

Retrieve an event

Retrieves a single event by its identifier. Use GET /v1/events/{event_id}/sessions to enumerate the event sessions. Returns 404 when the event does not exist or does not belong to your organization.

List event sessions

Retrieves the complete paginated list of sessions of an event, ordered by start date. Supports startAt range filters. Returns 404 when the event does not exist or does not belong to your organization.

Tickets

List tickets

Retrieves a paginated list of tickets belonging to your Billy organization sorted by their issuance date (issued_at DESC).

Retrieve a ticket

Retrieves a single ticket by its identifier — the same object `GET /tickets` lists, `transferable` included, so one ticket can be checked without paging through its event. Returns 404 when the ticket does not exist or does not belong to your organization.

Orders

List orders

Retrieves a paginated list of orders belonging to your Billy organization sorted by their creation date (created_at DESC).

Retrieve an order

Retrieves a single order by its identifier. Returns 404 when the order does not exist or does not belong to your organization.

Releases

The API is date-versioned. Each release target is documented separately, and every operation page has a switcher for the releases that describe it.

Prefer the machine-readable document? openapi.json serves the same content, with ?billy-api-version= selecting the release.