Changelog
What changed, and how versioning works.
Examples use a fictional festival, summer-fest. Sign in at events.grofomo.com and they switch to your own events.
How versioning works
The API is at apiVersion: 1, and stays there while changes are additive — new fields, new endpoints, new optional parameters.
Which means: ignore fields you do not recognise. A client that validates strictly against today's exact shape will break on a change designed not to break anything.
A genuinely breaking change would ship as a new version, announced here first, with the old one kept alive during the overlap.
Changes
These docs
This site is new. It documents the API as it stands today — including the API-key access control, which shipped shortly before it. Changes from here on are listed below as they happen.
Coming
Key requirements will extend to the remaining open endpoints. A handful of reads — event detail, content version, artist detail, announcements and organiser profile — currently answer without a key, because the Grofomo mobile app calls them without one. That will change once the app carries a credential.
We are measuring key adoption on those endpoints before making the switch, so it lands as a measured decision rather than a hopeful one. Send a key to them now: it is accepted and ignored today, so an integration built that way needs no change on the day.
An embeddable checkout, so you can sell from your own site. See selling tickets.