Ventrata OCTO API
Ventrata.comOCTO.travel
  • Welcome
  • Getting Started
    • Steps to Integrate
    • Glossary of Terms
    • Authentication
    • Test Credentials
    • Headers
    • Errors
    • Localization
  • Endpoints & Capabilities
  • OCTO Core
    • Suppliers
    • Products
    • Availability
    • Bookings
  • Capabilities
    • Pricing
    • Content
    • Pickups
    • Webhooks
    • Self-Service Mapping
    • Promotions / Offers
    • Custom Questions
    • Extras
    • Price Adjustments
    • Multi-Booking Cart
    • Card Payments
    • Resources
    • Packages
    • Gift Vouchers
    • Redemption
    • Online Check-in
    • Identities
    • Memberships
    • Rentals
  • Additional Resources
    • Ventrata Clients
    • Other OCTO Implementations
    • Support
    • FAQs
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Additional Resources

Other OCTO Implementations

PreviousVentrata ClientsNextSupport

Last updated 1 year ago

Was this helpful?

Apart from Ventrata and , the is widely adopted by other technology providers across attractions, tours, and activities sectors, including for example

  • Peek Pro (),

  • Zaui () ,

  • Xola,

  • Anchor,

and others.

This means you don't need to waste time building custom integrations to proprietary APIs and can establish connectivity with a growing list of OCTO-supporting booking/ticketing system providers in one development project. Consider this when planning and prioritizing your development project.

To learn more about OCTO members and join the initiative yourself, visit .

A group of volunteers also keep track of known OCTO implementations by suppliers (their booking/ticketing platforms) and resellers here:

our clients
OCTO API open standard
https://octodocs.peek.com/
https://docs.zaui.com/octo/
https://www.octo.travel/
https://docs.google.com/spreadsheets/d/1UIgUYAPO3SUsdoGmg5xIGHIBHWHOx7XfQCOzOTML6ms/