Ctrlk
Ventrata.comOCTO.travel
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Operator Connection (Backend) Terms

Additional terms for Operator Backend Partners — we connect out to your system so a Ventrata-powered Supplier can resell inventory you hold.

Last updated: October 6, 2026

Overview

These Terms apply if you are an Operator Backend Partner — we connect out to your system so a Ventrata-powered Supplier can resell inventory you hold.

They come together with the Ventrata Partner Terms, which you must also accept. Capitalized terms used here are defined there.

Where the Partner Terms conflict with these Terms, the Partner Terms prevail.

1. What this covers

You make an API available to us. We call it to:

  • retrieve availability and pricing;

  • create, amend, and cancel bookings; and

  • retrieve tickets,

so a Ventrata-powered Supplier can resell your inventory.

2. Whose terms apply

Your own developer or API terms govern our access to your API. These Terms sit alongside them and cover what each of us does to make the connection work. If your terms and these Terms conflict on the same point, tell us before we go live and we'll agree which applies.

3. Your API

Provide and maintain an API that conforms to the OCTO specification, and at minimum meets the OCTO Core endpoints and the response times published in the Documentation. In rare cases we may agree in writing to work with a non-OCTO API and build an adapter ourselves; where we do, your API must still deliver at least the functionality of OCTO Core. Where you connect to a further third-party system behind your own, these requirements still apply to your responses.

4. Changes and maintenance

Give us:

  • at least 3 months' notice before sunsetting a major version of your API;

  • at least 1 month's notice before a breaking change; and

  • reasonable notice of any planned maintenance that takes the API offline.

Emergency security changes are excepted.

5. Inventory and pricing

Availability, pricing, and product content you return must be accurate and current, and you're responsible for what you return to us. Where a booking fails or a cancellation doesn't propagate because of an outage or defect on your side, and the person who booked was entitled to cancel, we or the Ventrata-powered Supplier may cancel and refund regardless.

6. Commercial terms

Rates, commission, payment, and cancellation policy are agreed between you and the Ventrata-powered Supplier reselling your inventory. We're not party to that and hold no inventory risk.

7. Data

In this direction, personal data flows to you so you can fulfill the booking. You act as a Controller of that data, as set out in section 7.1 of the Partner Terms. Sections 7.3 to 7.12 of the Partner Terms apply, reading "Supplier Data" as data we send you.

8. Support and incidents

Each of us keeps a monitored technical contact and responds to the other's incident reports promptly; ours is connectivity@ventrata.com. Tell us within 24 hours of any issue affecting bookings, availability accuracy, ticket delivery, or security. You support your own customers; we support Suppliers on our platform.

9. Certification

Section 3 of the Partner Terms applies to you as it does to any other Partner. We certify your integration before go-live, we may re-test at any time, and if you stop meeting the requirements we may take any of the steps in section 3.10 — including revoking your Certification, removing your listing, disabling the connection, suspending, or terminating.

What else applies to you

Partner TermsAPI Terms

Questions about any of this? Email connectivity@ventrata.com. We'd rather explain a clause than have you guess at it.

PreviousAPI Terms