integrate a reseller or single-instance booking system with a zaui-powered supplier via octo or zapi

Steps

1. pick the right API: resellers/OTAs/marketplaces connecting to one or more Zaui suppliers use the OCTO Specification (JSON, current); the legacy I/O Specification (XML) is deprecated
2. for OCTO, note Zaui is a founding member of the OCTO community and implements the core spec plus optional capabilities: Content, Pricing, Pickups, GT-Locations, and GT-Connections, the last two extending OCTO to ground transportation
3. since April 2024, OCTO endpoints no longer require a supplier ID in the URL path, and Zaui issues one API key per reseller-supplier pair rather than a single key per reseller; email Zaui's connectivity team for supplier connections or the legacy spec
4. the OCTO API with Zaui is free to use, with direct integrations already in place with channels such as major OTAs and marketplaces
5. for a deeper single-supplier integration (e.g., internal CRM, HR, payroll, accounting systems), use the Supplier API (ZAPI, XML/JSON) instead — Zaui explicitly recommends trying Webhooks + Zapier first before committing to a full ZAPI integration
6. to have data pushed to your own endpoints, subscribe to Zaui's Web-hook Specification (JSON) rather than polling