API reference

Everything an event website needs: the published lineup, FAQs, news, announcements, ticket availability, merch, and forms. All responses are JSON, all reads are cacheable, and every example below is generated from the same schemas the API is built from.

Event

Event detail
Core event info: dates, venue, stages and brand.
GET/v1/events/{slug}
Content version
A cheap probe for "has anything changed?".
GET/v1/events/{slug}/version
Organiser profile
Organiser bio, branding and their upcoming events.
GET/v1/organisers/{slug}

Lineup

Content

Tickets & merch

Forms & signups

Discovery

Event search
Search public events across all organisers.
GET/v1/events/search

Deliberately not documented

The mobile app's device endpoints, the door scanner's check-in surface, wallet passes, ticket capability links and the raw checkout flow (quote, reserve, pay) are all internal. Selling tickets from your own site will arrive as a drop-in embed rather than as a documented write API — see selling tickets. These are omissions by decision, not gaps.