githubEdit

Steps to Integrate

A practical process for integrating with Ventrata's OCTO API for resellers

circle-info

This page provides a step-by-step overview for resellers connecting to suppliers that use Ventrata. For other use cases (for example, a Ventrata client building their own checkout or an operator connection), contact [email protected]envelope.

1

Step 1: Review Documentation and Plan

Review this documentation and familiarize your team with the OCTO API and Ventrata's implementation.

Decide which Endpoints and Capabilities you will implement. Ventrata requires all resellers to support OCTO core endpoints as a minimum:

Implementing capabilities is optional, but Ventrata strongly recommends at least Pricing, because dynamic pricing is now widely used by Ventrata clients.

Contact us if you have implementation questions or want to discuss specific capabilities.

2

Step 2: Develop

Build the integration. Most resellers complete development in 2 to 10 days. If you already support OCTO with another booking or ticketing system, you can usually proceed directly to testing.

Test as you build using Ventrata's EdinExplore account, a fictional supplier created for this purpose. It includes common product configurations and gives access to products, bookings, and API logs. See Test Credentials for access.

3

Step 3: Test

After self-testing your implementation with EdinExplore, contact [email protected]envelope for integration review and approval.

The review response target is 1 to 2 business days. We may ask for additional test bookings (including updates and cancellations), a voucher sample, and confirmation of supported capabilities before go-live approval.

4

Step 4: Go Live

After approval, your integration is added to Ventrata's partner list and documented in our helpdeskarrow-up-right, so suppliers can enable it and share API keys with your team.

At that point, you can contact Ventrata clients to connect products and begin selling.

Last updated