Guided view New to this? Every page opens with a plain-language explanation before the detail begins, and terms like hospitality, concours and biennale are explained where they appear.
Expert view You already know the vocabulary. Straight to the substance, with the introductory explanations hidden. This is the default.
A bounded, read-only JSON API for events, dates, destinations, circuits, overlaps and the where-now view. Every response carries provenance and the terms of reuse. There is no endpoint that returns everything.
Endpoints
GET /api/v1/search?q=Search events, destinations, circuits, months and categories (max 10).
GET /api/v1/events/{slug}One event in full, with every dated edition, its status, note and source.
GET /api/v1/events?category=&destination=&circuit=&month=Bounded listing: 20 per call; offset ≤ 100 without a key.
GET /api/v1/calendar?from=&to=Dated editions in a window of at most 62 days; filters category, region, destination, min.
GET /api/v1/where-nowThis week, next week, the next 30 days, the next major move and the season line.
GET /api/v1/destinations/{slug}A destination with its events, month-by-month activity, airports, marinas, climate and nearby places.
GET /api/v1/circuits/{slug}A circuit’s ordered stops with their next dates.
GET /api/v1/overlaps?event=Events overlapping an event’s next edition: same destination, nearby (with km), same country.
GET /api/v1/categoriesThe taxonomy with counts.
Representations and feeds
Every event is also served as HTML, JSON (.json), Markdown (.md) and iCalendar (.ics) from one record. Subscribe-able ICS feeds exist for the global calendar (/calendar.ics), each circuit, category and destination.
Limits
Anonymous use is rate-limited per IP (30 API calls a minute) and listings stop at offset 100. Keys with higher quotas are available by arrangement for applications that carry the provenance fields through and respect the Terms of Use. Bulk extraction, database reproduction and commercial republication are not permitted. Request a key.