Overview 01 Start with a free key 02 Getting started 03 Authentication 04 MCP server for Claude and ChatGPT 05 MCP tools 06 What we cover 07 The whole API in one file 08 Data integrity 09 Data freshness and release calendar 10 Revisions 11 Historical data and bulk downloads 12 The response envelope 13 Schemas 14 Batch requests 15 Pagination 16 Errors 17 Periods, dates and frequencies 18 Units, scaling and currencies 19 Definitions differ between countries 20 Breakdowns 21 Destinations: regions and cities 22 Joining holidays and exchange rates 23 How the statistics are made 24 Rate limits 25 Webhooks for new releases 26 Changelog All countries One country Country coverage Latest figures How it is counted Methods, every country Coverage and counts World regions Regional totals Country peers Country brief Rivals Advisories scale Advisories Advisory changes Advisory for a destination Arrivals Nights Visitor spend Departures Occupancy Capacity Destinations Venues Weather Hotel rates Seats Arrivals by origin Nights by accommodation Nights by region Arrivals by purpose Outbound destinations Find series One series Series values Revisions Series metadata Search series Source tables Series latest Compare countries Rankings Growth Market share Seasonality Movers Records Seasons, every country Seasons Yearly totals Direction of travel Trend Recovery Benchmark Length of stay Forecast Nowcast Anomalies Origin shift Concentration FX sensitivity Tourism intensity Public holidays Country holidays Holiday join Upcoming holidays Holidays on a date School holidays Long weekends Holidays by month Fares Prices Exchange rates One currency Convert spend Latest rates Fuel prices Latest fuel prices Cross-rate grid Economy Economy and tourism Economic outlook Country reference Time zones What is held Population, every country Population profile Age pyramid Population history Censuses Releases Latest releases Freshness Data gaps Release calendar Changelog World Tourism Monitor Monitor editions Monitor paper World tourism index Trust index Country download Full archive Units Your usage Status
Authentication
How keys work: the header, live and test keys, rotation with overlap.
Guide
Send the key on every request in either of two headers: X-API-Key: your_key, or Authorization: Bearer your_key. Both are read the same way. A key in the address (?key=) is refused with a 400, so keys never land in server logs.
curl https://api.tourismapi.com/v1/countries \
-H "X-API-Key: $TOURISM_API_KEY"
curl https://api.tourismapi.com/v1/countries \
-H "Authorization: Bearer $TOURISM_API_KEY" Prefix Use ta_live_ Production calls, counted against your plan ta_test_ The free key: same shapes, the free endpoints only
To rotate, create a second key in your account, deploy it, then revoke the first. Both work during the overlap. We only ever show the first characters of a key after it is made; the secret itself is never stored in readable form.
Browser code exposes any key it ships with. Call the API from your own server and pass the figures on.
