Introduction
Build smarter products with connected data across events, museums, dining, gardens, walks, wildlife, galleries, and more. One coordinate in, structured JSON out — sourced from authoritative UK institutions (National Trust, RHS, MICHELIN, Mapping Museums, UNESCO, DarkSky International, iNaturalist, Ticketmaster, Open-Meteo), cached at the edge, attributed at the source.
Drop the pre-composed HTML widget into any page in a single
<iframe>, or compose the JSON sections yourself.
Who this is for
What’s in the API
Six topic areas, ordered by day-planning weight:
- Places to Visit — curated day-trip destinations: 240 RHS
Partner Gardens (UK), ~600 National Trust properties + 1,201 NT walks
(UK), 1,273 UNESCO World Heritage Sites (global), 295 DarkSky-
certified Dark Sky Places (global), 3,360 Mapping-Museums UK
museums, plus an
arts-filtered art galleries subset. 7 endpoints. - Events & Activities — ticketed events during the stay, curated annual festivals, and bookable tours and experiences. 3 endpoints.
- Dining — MICHELIN-recognised restaurants (three-star, two-star, one-star, Bib Gourmand, Selected), tier-ranked and radius-filtered by prestige. 1 endpoint.
- Local Wildlife — species commonly observed near the coord in the month of the visit, aggregated across years of citizen-science observation data. 1 endpoint.
- Weather — forecast + climatology, sunrise and sunset times, marine (waves + sea temp), snow (alpine only). 4 endpoints.
- Journey Planner — nearest airports with drive-time estimates plus an interactive directions embed. 1 endpoint.
Every endpoint self-gates via an applicable flag — marine data on
an inland coord returns applicable: false so you hide the section
rather than branching on an error.
Design principles
UK-strong, global where it makes sense. Half the datasets are
UK-authoritative (RHS, NT, Mapping Museums). The other half are
global (UNESCO, DarkSky, weather, MICHELIN). The API tells you which
via the applicable flag — you don’t have to guess.
Facts, attributed. Every response carries a sources[] array.
We republish only facts (name, coord, tier, subject) — never
copyrighted editorial content or images.
Cached at the edge. Every response carries a meta.fresh_until
timestamp. You never need to think about upstream rate limits.
Where to start
- Getting started — grab a key, make your first call, embed the widget.
- Chora overview — every endpoint in one place, with composition examples.
- Places to Visit — the flagship dataset stack.
- Embed the widget — one
<iframe>, themeable, auto-resizes. - Authentication — Bearer token, one key per environment.
- Attribution — how to credit upstream data providers.
Base URL
Status
- Live status: /v1/status
- Liveness probe: /v1/health