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 Joining holidays and exchange rates 22 How the statistics are made 23 Rate limits 24 Webhooks for new releases 25 Changelog All countries One country Country coverage Latest figures World regions Regional totals Country peers Country brief Rivals Find series One series Series values Revisions Series metadata Search series Source tables Series latest Arrivals Nights Visitor spend Departures Occupancy Capacity Arrivals by origin Nights by accommodation Nights by region Arrivals by purpose Outbound destinations Compare countries Rankings Growth Market share Seasonality Movers Records Trend Recovery Benchmark Length of stay Forecast Nowcast Anomalies Origin shift Concentration FX sensitivity Tourism intensity Public holidays Country holidays Exchange rates One currency Convert spend Holiday join Upcoming holidays Latest rates Fuel prices Latest fuel prices Economy Economy and tourism Economic outlook 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
Revisions
Offices change published figures. Every change is kept, with both values.
Guide
When an office revises a figure, the new value replaces the old one in every endpoint, and the change is recorded: period, old value, new value and when we saw it. Use it to keep a model in step without reloading everything.
curl "https://api.tourismapi.com/v1/series/it.nights.total.m/revisions?since=2026-10-01T00:00:00Z" \
-H "X-API-Key: $TOURISM_API_KEY"
