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
  • Step 1 - Review Documentation & Plan
  • Step 2 - Develop
  • Step 3 - Test
  • Step 4 - Go Live!

Was this helpful?

Edit on GitHub
  1. Getting Started

Steps to Integrate

Quick & easy process to integrate with Ventrata's OCTO API for Resellers

PreviousWelcomeNextGlossary of Terms

Last updated 5 months ago

Was this helpful?

The page provides a step-by-step overview of the integration process for resellers looking to connect with suppliers using Ventrata. If you're looking to use Ventrata's OCTO API for other use cases (e.g. Ventrata client building own checkout, operator connection, etc.), please reach out to for additional information.

Step 1 - Review Documentation & Plan

Review this documentation, and familiarize yourself with the OCTO API and Ventrata's implementation of it.

Decide which you are going to implement. Ventrata requires all resellers to support OCTO Core endpoints, such as , , and as a minimum implementation.

Implementing capabilities is optional, but we strongly suggest Resellers support at least as this will be required to work with the majority of due increasing adoption of our dynamic pricing functionality. Feel free to get in touch if you have any questions or if you’d like to discuss the implementation and specific capabilities.

Step 2 - Develop

Write your code. In our experience, most Resellers have been able to complete development in 2 to 10 days. If you already support OCTO API with another booking/ticketing system, you should be able to proceed to without any major development.

You can easily test your integration as you progress with the help of Ventrata's EdinExplore - a fictional supplier account we've created for this. This account has all the most common product configurations, can be used for any amount of testing you need, and allows you to view products, bookings, as well as Ventrata's API logs. See for access.

Step 3 - Test

Once you've self-tested your implementation with the EdinExplore account, please reach out to to have our team review and approve your integration.

We value your time and aim to get back to you on this within 1-2 business days. We will ask you to perform a few additional test bookings, amend, cancel them, share your voucher, and review capabilities supported before approving you to go live.

Step 4 - Go Live!

Upon approval, you will be added to the list of partners in the Ventrata system, along with the integration instructions added to our , making it easy for suppliers to enable the integration and share the API key with your team.

This is when you can reach out to to connect their products and start selling.

connectivity@ventrata.com
Endpoints and Capabilities
Products
Availability
Booking
Pricing
Ventrata clients
testing
Test Credentials
connectivity@ventrata.com
helpdesk
Ventrata clients