Skip to main content
GET
Get a ticket by ID

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

The ID of the resource to query by

Response

Default Response

A ticket that is associated to an event and race.

id
string
required

A unique identifier for the ticket.

title
string
required

The name of the ticket

titleByLocale
object
required

Ticket title translated to multiple locales.

Will always include the default title, and may also specify translations in a number of other locales.

Example:
ticketSlug
string
required

The slug of the ticket — a stable public identifier

raceId
string
required

The unique identifier of the associated race

raceTitle
string
required

The name of the associated race

price
Price · object
required

A monetary value in 100x base unit format. For example, 1 GBP is represented as: { "value": 100, "currencyCode": "GBP" }

And 5 cents are represented as: { "value": 5, "currencyCode": "USD" }

availability
enum<string>
required

Whether a ticket can be booked, and if not, why.

Derived rather than configured: it folds the organizer's availability setting together with sold-out, expiry, on-sale date and deletion, so it answers what a buyer would actually experience rather than what was set up.

Available options:
AVAILABLE,
SOLD_OUT,
CLOSED,
COMING_SOON,
NOT_AVAILABLE
isDeleted
boolean
required

Whether the organizer has deleted this ticket.

A deleted ticket stops appearing in any ticket list, but stays readable by id, because bookings outlive it — every booking carries the ticketId it was made against, and that reference has to keep resolving. availability reports a deleted ticket as NOT_AVAILABLE, which does not distinguish it from one the organizer merely switched off; this does.

Example:

false

description
string

The description of the ticket