Skip to main content

How to Request a New API Connection or Partner

How to introduce a new reseller, operator backend or software partner to Ventrata, or start your own custom connection, and what happens from introduction to certification.

Can't find a partner in the List of Supported Connections & Partners? Every new connection starts the same way: you introduce the partner to us by email, and we take it from there. We move quickly and support the partner through to go-live. New to connections? Start with Connections & Partners Explained.

📒 NOTE

Before you request a connection, search the Help Center or ask Venny, our AI assistant, in the chat. The connection may already exist or be in development.

How we work

  • Shared Slack channels. Developers like working in Slack, so when a project kicks off after the introduction, we set up a shared Slack channel with the partner (and with you, if you'd like to follow along).

  • Hands-on support. We run a kickoff call, answer technical questions and test with the partner until the connection is live.

  • Every request is reviewed. We're open to new connections and review every request. Occasionally a project isn't the right fit, and if so we'll tell you early.

Reseller Connections

You want to sell your products through a reseller (OTA, marketplace, pass or other distributor) that isn't connected yet.

  1. Introduce the reseller by email to [email protected] and Dominic Martinkevic, Head of Partnerships ([email protected]), and share our documentation at docs.ventrata.com. If you know which system provider the reseller uses, copy them in too. Otherwise we'll work it out together.

  2. We take it from here. We help the reseller build the business case, look at which Ventrata clients they work with, and agree the most effective way to integrate.

  3. The reseller builds the integration. Most resellers complete development in 2 to 10 business days of active work (see Steps to Integrate).

  4. They certify, first with OCTO, then with Ventrata. Once listed in the Partner Gallery, you can connect them in your Dashboard.

Integration approach

Our preferred way is the OCTO API. Ventrata offers an OCTO-compliant API, documented at docs.ventrata.com. We prioritize direct integrations and typically don't integrate through third-party channel managers. Occasionally we consider other approaches, to be discussed with each partner early in the project.

Operator Backends & Connections

You want to resell another operator's products directly from Ventrata.

  1. Introduce the operator by email to [email protected] and Dominic Martinkevic, Head of Partnerships ([email protected]). If you know which booking or ticketing system they use, copy that provider in too. Otherwise we'll work it out together.

  2. We take it from here. We agree the scope with the operator and their system provider.

  3. They provide an API for resellers, either one they already have or one they develop.

  4. They certify, first with OCTO, then with Ventrata. The connection then becomes available in your account.

Integration approach

Our preferred way is an OCTO API that follows the OCTO standard. Occasionally we may consider a custom API already available from the provider, or an API that follows the Viator Supplier API specification, to be discussed.

Apps & Software

You want to connect a tool such as a CRM, pricing, analytics or messaging platform.

  1. Introduce the software provider by email to [email protected] and Dominic Martinkevic, Head of Partnerships ([email protected]), with details of the project.

  2. We take it from here. We scope the needs with the provider and share documentation for the use case.

  3. The provider builds the integration with our support.

  4. They certify with Ventrata (see Certification). The app then becomes available to connect in your Dashboard.

Integration approach

Where possible we base app integrations on the OCTO standard. Ventrata has dozens of custom capabilities built on top of OCTO, and we share private documentation for each use case directly with the partner.

Your Custom Connections

You want to build your own API connection for internal use, such as your own checkout or reporting.

  1. Email [email protected] or your Customer Success Manager, outlining what you're building.

  2. We take it from here. We share documentation for your use case and support your developers.

  3. Your custom connection appears in your account, ready to use. No certification is needed, and we aim to move quickly so your project isn't blocked.

Integration approach

Custom connections use our OCTO API (docs.ventrata.com) and, where needed, Ventrata's custom capabilities built on top of OCTO. We share private documentation for your use case directly with your team.

What to include in your email

  • What you're trying to achieve, and the ideal scope

  • Your timeline or target launch date

  • Similar integrations the partner already has, if any

  • Other Ventrata clients the partner wants to connect with, if you know

📗 TIP

A short introduction is enough, for example: "Hi [partner], meet Ventrata's connectivity team, copied here. We'd love to sell our tours through you. Their docs are at docs.ventrata.com, and they'll help you plan the integration. We're hoping to launch by [date]."

Related Articles
Did this answer your question?