Introduction
Chora gives every property page the same rich context a concierge would: weather during the stay, sunrise and sunset times, nearest airports, what’s on locally, MICHELIN restaurants, and seasonal wildlife. One coordinate in, structured JSON out — sourced from trusted upstreams, cached at the edge, attributed at the source.
Drop the pre-composed HTML widget into a property page in a single
<iframe>, or compose the JSON sections yourself in your own booking
flow.
Who this is for
- OTAs and booking platforms adding contextual data to property detail pages without maintaining a dozen upstream integrations.
- Vacation rental hosts and channel managers enriching listings with weather, transport, and things-to-do during the stay.
- Property owners self-serve — one
<iframe>on your Wix, Squarespace, or WordPress site.
What’s in the API
Five topic areas, matching the sections in your booking page:
- Weather — forecast + climatology, sunrise and sunset times, marine (waves + sea temp), snow (alpine only). 4 endpoints.
- Journey Planner — nearest airports with drive-time estimates, interactive directions embed, and nearby amenities within walking distance. 2 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. 2 endpoints.
- Local Wildlife — species commonly observed near the coord in the month of the visit, aggregated across years of citizen-science observation data. 1 endpoint.
- 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), and 295 DarkSky- certified Dark Sky Places (global). 5 endpoints.
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
Booking-safe. No travel advisories, no safety warnings, no cost-of-living data. Nothing Chora returns would discourage a booking.
Facts, attributed. Every response carries a sources[] array.
We republish only facts (name, coord, tier, cuisine) — 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.
- Embed the widget — one
<iframe>, themeable, auto-resizes. - Authentication — Bearer token, one key per environment.
- Rate limits — headers you can rely on.
- Attribution — how to credit upstream data providers.
Base URL
Status
- Live status: /v1/status
- Liveness probe: /v1/health