Grofomo API
Browse the docs

For AI agents

Machine-readable entry points: llms.txt, markdown twins and an OpenAPI document.

Examples use a fictional festival, summer-fest. Sign in at events.grofomo.com and they switch to your own events.

These docs are built to be read by coding assistants as well as people. Everything below is public and needs no key.

Entry points

URLWhat it is
/llms.txtA map of the whole site: every page, one line each. Start here.
/llms-full.txtEvery page's full text in one file.
/openapi.jsonOpenAPI 3.1 for every documented endpoint, generated from the same schemas the API uses.

Markdown twins

Any page has a plain-markdown version at the same path with .md appended:

curl https://developers.grofomo.com/reference/events/lineup.md

Or ask for it by content type at the canonical URL:

curl -H 'Accept: text/markdown' \
  https://developers.grofomo.com/reference/events/lineup

Same document either way — no navigation, no markup, no tokens spent on chrome.

Pointing an assistant at this

Read https://developers.grofomo.com/llms.txt for the Grofomo event API,
then build a lineup page for the event with slug "summer-fest".

Send the key in an X-Grofomo-Key header, and remember ?surface=web.

Things worth telling it explicitly

Three mistakes we see repeatedly, all easy to state up front:

  1. ?surface=web is required on most endpoints. Omitting it silently selects the mobile-app surface and can return 404 for a live event.
  2. Publishable keys (pk_live_…) belong in browser code; secret keys (sk_live_…) never do. Choose by where the code runs.
  3. Read soldOut, not available. available is null both for unlimited tiers and for organisers who hide counts.