A few markets are deep, most are working-class, a long tail is honest-gap. Pick the tier that matches the markets your customers actually buy.
We do not promise a refresh rhythm. These dates come from our data ledger of 11 November 2026 and from our database on 12 November 2026. Our scheduled watchers publish their last run times at api.travelminds.ai/v1/freshness.
| Dataset | Last loaded |
|---|---|
| Government travel advisories (Canada: the country-wide risk level from its open dataset; France, New Zealand, United Kingdom, United States) | 11 November 2026 (the United Kingdom run was still in progress that evening); Canada 13 November 2026 |
| Other open sources reloaded the same day, among them heritage registers, Who's On First places, UN/LOCODE, public holidays, Wikidata festivals, MusicBrainz events, Pleiades, World Bank indicators, Eurostat tourism statistics, geoBoundaries and Natural Earth | 11 November 2026 |
| Places (points of interest) | Rows added from April to July 2026, and again in November 2026 |
| Hotels | Last row added 2 July 2026 |
| Restaurants | Last row added 2 July 2026 |
| Cities | Last city added 16 May 2026 |
| City narratives | Last updated 30 June 2026 |
| Climate averages | 3 July 2026 |
| France tourism places (DATAtourisme) | The copy we read has not changed since 2 July 2026 |
| Events and festivals (about 53,000 rows) | Loaded once by hand, last on 23 June 2026 |
| Neighbour cache behind nearby-place lookups | Last built 20 May 2026 |
| Visa rules | Last changed 16 to 26 April 2026 |
Bulk file deltas are available on request.
Markets where our data is deepest. State-level admin hierarchy, named tourism circuits, ASI / UNESCO grounding, multilingual narratives.
Major destination markets with full restaurant + hotel + POI coverage and city-level narratives. Suitable for direct production deployment in itinerary / chatbot / booking-companion products.
Smaller markets and emerging destinations with a working narrative layer + dependable POI density in capital + top-5 cities. Use directly for general-purpose travel agents; double-check for hyper-local accuracy if you're building a destination-specialist product.
Boutique-tourism markets where we have the headline destinations covered but mid-tier and budget inventory is sparse. Our response models flag premium_only: true on these — your integration should surface that to your traveller instead of overpromising.
Markets where coverage is genuinely thin and the API returns coverage: "sparse" by design. Your integration should fall through to the consulate / official advisory rather than fake a confident answer.
Per-country coverage page with counts (cities, POIs, restaurants, hotels, narratives) as of 12 November 2026, counted by the rules the API serves by.
Maps can mislead: a country shaded "covered" can mean "we have one row for the capital." Our coverage page tells you the texture of the data — how deep, how recent, where the gaps are. If your buyer is selling into India / the US / Japan, you'll be working at Tier A or Tier B all day. If your buyer asks about Tuvalu, you'll know to architect for the no-data path before the integration starts.
Need a tier that doesn't exist yet for a market you're entering? Tell us which market at [email protected].
Comparing options? See where our coverage approach diverges from raw OpenStreetMap, Wikipedia scraping, Google Places, and Sabre's GDS data.