Build an event website on live festival data.
Organisers run their festival in Grofomo — lineup, stages, set times, FAQs, news, tickets, merch. This API hands you that same data as JSON, already published and already public, so the site you build stays right without anyone re-typing a running order into a CMS.
One request
Ask the organiser for a publishable key, send it, and read the published lineup.
curl -sS \
-H 'X-Grofomo-Key: pk_live_YOUR_PUBLISHABLE_KEY' \
'https://api.grofomo.com/v1/events/summer-fest/lineup?surface=web'Examples use a fictional festival, summer-fest. Sign in at events.grofomo.com and they switch to your own events.
Where to go next
Quickstart
Your first request, and a working lineup page in about ten minutes.
For organisers
Give your web developer a key, and choose which domains may use it.
Authentication
Publishable and secret keys, where each one belongs, and the two failure codes.
Surfaces
Why every website request needs `?surface=web`, and what happens without it.
Responses and errors
The response envelope, the error shape, and how to tell them apart.
Caching and rate limits
How long each feed is cached, and how to poll cheaply.
CORS and allowed domains
What the domain allowlist does, and the thing it deliberately does not do.
Webhooks
Receive ticket sales and signups on your own endpoint, with signature verification.
Selling tickets
How to sell from your own site today, and the embed that is coming.
For AI agents
Machine-readable entry points: llms.txt, markdown twins and an OpenAPI document.
Changelog
What changed, and how versioning works.