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

Event lineup
Published lineup: artists, stages and set times.
GET/v1/events/{slug}/lineup
Artist detail
Full artist profile, plus their sets at this event.
GET/v1/events/{slug}/artists/{artistId}

Content

Event FAQs
Categorised FAQs, with answers pre-rendered to HTML.
GET/v1/events/{slug}/faq
Photo gallery
Curated photos the organiser picked for their website.
GET/v1/events/{slug}/gallery
News index
Published news articles, newest first.
GET/v1/events/{slug}/news
News article
A single published article, with its full body.
GET/v1/events/{slug}/news/{articleSlug}
Announcements
Announcements the organiser has sent, newest first.
GET/v1/events/{slug}/broadcasts

Tickets & merch

Ticket availability
Visible ticket types and release tiers, with live availability.
GET/v1/events/{slug}/tickets
Quote a cart
Price a cart and check a promo code, without holding anything.
POST/v1/events/{slug}/tickets/quote
Reserve tickets
Hold the cart for 15 minutes and create the order.
POST/v1/events/{slug}/tickets/reserve
Buyer details and consent
Attach the buyer's email, name, phone and marketing consent to a reserved order.
PATCH/v1/events/{slug}/tickets/orders/{checkoutToken}
Start payment
Get the Stripe client secret to take the card on your page.
POST/v1/events/{slug}/tickets/orders/{checkoutToken}/pay
Complete a free order
Issue the tickets for a zero-total order, with no card step.
POST/v1/events/{slug}/tickets/orders/{checkoutToken}/complete-free
Order status
Where the order is, its lines and totals, and what the buyer earned.
GET/v1/events/{slug}/tickets/orders/{checkoutToken}
Funnel beacon
Tell the organiser's sales report that a visitor viewed or selected tickets.
POST/v1/events/{slug}/tickets/funnel
Merch catalogue
Garments, colours, sizes, print zones and prices.
GET/v1/events/{slug}/merch

Forms & signups

Mailing-list signup
Add an email to the organiser's mailing list from your own form.
POST/v1/events/{slug}/subscribe
Prelaunch form
The published prelaunch registration form, so you can render it yourself.
GET/v1/events/{slug}/prelaunch
Prelaunch registration
Register interest in the event from your own prelaunch form.
POST/v1/events/{slug}/prelaunch/register
Prelaunch verification
Type back the SMS code, or ask for the email or code again.
POST/v1/events/{slug}/prelaunch/verify
Form definition
The fields of a published form, so you can render it yourself.
GET/v1/forms/{key}
Submit a form
Send answers back for a published form.
POST/v1/forms/{key}/submissions

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 and ticket capability links are internal. These are omissions by decision, not gaps. Selling tickets from your own site is documented: see selling tickets.