Public APIs
Izi favicon

Izi

Transportation

Audio guide for travellers.

Izi's website screenshot

About Izi

The izi.TRAVEL API provides programmatic access to the izi.TRAVEL Directory (MTG Content Directory), a database of audio guide content for museums, tours, and points of interest. Requests are made over HTTPS and return JSON, with authentication handled via an X-IZI-API-KEY header (or an api_key parameter for debugging). Responses are versioned, with specific API versions enabling features such as Museum Tours, which model navigational stories between exhibits within collections, and Quests, a gamified playback type that divides a tour into segments unlocked through conditions like quiz answers or trigger-zone visits.

The API exposes endpoints for retrieving objects (museums, collections, tours, exhibits) in compact or full form, including metadata such as children counts, audio duration, size, and playback structure. Playback types include sequential, random, and quest, with the quest type built from segments, tourist attractions, navigational points, open-segment conditions, and end-quest conditions.

This API is intended for developers building applications that consume or integrate izi.TRAVEL's audio guide content, such as museum tour apps or gamified quest experiences based on tourist attractions and navigational points.

Key features

  • Access museum tours, exhibits, and audio guide content via REST API
  • Museum Tours feature with ordered navigational stories between exhibits
  • Gamified quest-style playback with branching segments based on quiz answers or trigger zones
  • JSON responses over HTTPS with UTF-8 encoding
  • Endpoint to fetch children count and ordered children for a collection

Frequently asked questions

What authentication does the izi.TRAVEL API require?

All requests require an API key passed via the X-IZI-API-KEY header, or optionally via an api_key parameter for debugging.

What data format does the API return?

All responses are JSON objects or arrays encoded in UTF-8, with HTTP status codes indicating success or failure.

What can I build with the izi.TRAVEL API?

You can access museum tours, exhibits, and quest-based audio guides, including navigational stories and gamified segment unlocking based on quiz results or trigger zones.

How are errors reported by the API?

Failed requests return a JSON body containing code and error fields for debugging, alongside generic error codes applicable to all requests.

Advertise here

Featured products

  • SerpApi - Search API favicon
  • Screenshot Scout favicon
  • TalorData favicon
  • CoreClaw favicon

Show your product to thousands of developers

· 100k monthly pageviews
· 7k newsletter subscribers

Advertise your product