Plug into the data

Five entry points

GET /api/dataset.json

The full set, paginated (limit, offset). Nested fields: hours by season, prices by category.

GET /api/dataset.csv

One row per château, flat columns. UTF-8 with BOM so it opens correctly in Excel.

GET /api/chateau/{slug}.json

A single entry. Each practical field carries its source and verification date.

GET /en/castle/{slug}.md

The same entry in Markdown, with no navigation and no script. Append .md to any entry URL, in all three languages. No key needed.

GET /llms.txt

Corpus description, licence, how to cite us, and entry points. No key needed.

Authentication

The key goes in the Authorization header. A ?key= parameter is accepted for tools that cannot send headers, but it ends up in proxy logs: prefer the header.

curl -H "Authorization: Bearer ck_live_…" \
  https://chateaupedia.com/api/dataset.json?limit=100

Limits

• 5,000 calls per day per key. Write to us if you need more — it is usually granted.
• Only published entries are exposed. An entry still being verified does not appear.
• A field whose verification has expired is not returned, rather than returned stale.

Licence

ODbL 1.0. You may reuse, modify and redistribute, commercially included, provided you credit Chateaupedia and share the same freedoms on derived data.