OCTO Specification and Zaui
OCTO (Open Connectivity for Tour, Activities and Attractions) Connecting resellers with suppliers of attractions, activities, tours and ground transportation products and services.
Last updated
OCTO (Open Connectivity for Tour, Activities and Attractions) Connecting resellers with suppliers of attractions, activities, tours and ground transportation products and services.
Last updated
Welcome to Zaui's API Developer Documentation.
This documentation outlines Zaui's implementation of the OCTO API Specification for Resellers, Online Travel Agents (OTA's), Marketplaces, developers and other distributors looking to establish API with suppliers that use Zaui as their ticketing platform.
Zaui is both a founding member and supporting member of the OCTO community.
Zaui is an enterprise ticketing platform designed for tours, activities and attraction (the "things to do") operators anywhere in the world. Our online platform is available in over 19 languages and enables online, in-person and third-party sales. Our platform has 100's of external integrations available in our Marketplace of Apps and Integrations available to customize your platform.
In addition to the "things to do", Zaui's platform is designed for all types of ground transportation, privates and charters along with complex Intercity style operations.
Resellers, OTA's, Marketplaces, developers and third party platforms integrate directly with Zaui using the OCTO API to access supplier's inventory, pricing and more.
Direct integrations with Zaui are supported with industry leads such as Viator, GetYourGuide, Expedia, Klook, Headout, TUI Musement, Tiqets and many more.
Learn more about Zaui at https://www.zaui.com
The OCTO API with Zaui is FREE TO USE.
This documentation details Zaui Software's implementation of the OCTo API Specification which is an open API standard initiative for the experiences industry. More information about the OCTo specification and who's part of it can be read here: https://www.octo.travel/.
Please note, that as of April 2024, we have upgraded our OCTO implementation such that a supplier ID is no longer required as part of the endpoint path. Previously, this was the case, but this way of structuring endpoints was discontinued from the official OCTO specification. Additionally, an API key will be issued for each reseller <> supplier pair, whereas previously, only one API was issued for each reseller. However, this change is backwards compatible and requests to our original endpoints are still valid and will yield a response. If you would like a copy of the original specification, please email us at connectivity@zaui.com.
In addition to all the attractions, activities and tours products, supported through the OCTo specification, we at Zaui, have extended our implementation to also support ground transportation(GT) services, using the same specification.
Zaui implements the core OCTO specification and also provides the following optional capabilities:
Content
Pricing
Pickups
GT-Locations
GT-Connections
