> For the complete documentation index, see [llms.txt](https://docs.ventrata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ventrata.com/readme.md).

# Welcome

Connect to attractions, tours, and activities running on Ventrata through the OCTO API — one integration, every supplier who switches you on.

This documentation covers Ventrata's implementation of the [OCTO API Specification](https://docs.octo.travel/), for resellers — OTAs, marketplaces, city card operators, and other distributors — connecting to suppliers that use Ventrata as their ticketing platform.

You build once. Every Ventrata-powered supplier who switches you on is then reachable through the same integration, with no per-supplier development.

![OCTO Founding Member](https://221588849-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M7bgGIyO7QYNOfUMfxh%2Fuploads%2FMYOxyG8Nzu1gSNp85je4%2Focto-badge-founding-member.svg?alt=media\&token=5571066b-3299-48cb-ac90-aace0d1752ff) ![OCTO Supported](https://221588849-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M7bgGIyO7QYNOfUMfxh%2Fuploads%2Flx8982UomnWwUH72yaKj%2Focto-badge-supported.svg?alt=media\&token=8b7cc705-e883-439c-a17b-074172028df1)

{% hint style="success" %}
**No fees, and a free test account.** There is no charge for resellers working with Ventrata clients to use the OCTO API or the support that comes with it — and you can build and test against our test Supplier account before you are certified.
{% endhint %}

## About OCTO

OCTO (Open Connectivity for Tours, Activities and Attractions) is an open standard API specification for the in-destination experiences sector. It defines agreed schemas, endpoints, and capabilities for connecting reservation systems, resellers, OTAs, and other technology in tours, activities, and attractions. It is developed and administered by a member-based not-for-profit, OCTO Standards NP Inc.

Ventrata is a founding member and one of the earliest adopters. OCTO is also implemented by Peek Pro, Xola, Zaui, Anchor, and others — so the work you do here carries over to other platforms.

{% content-ref url="/pages/7pZaVA4eq2BXbMsFXfoj" %}
[Other OCTO Implementations](/additional-resources/other-octo-implementations.md)
{% endcontent-ref %}

Learn more about OCTO, including how to become a member, at [octo.travel](https://www.octo.travel/). The official specifications are published at [docs.octo.travel](https://docs.octo.travel/) and [github.com/octotravel](https://github.com/octotravel).

## Who you'll connect to

Ventrata is an enterprise ticketing platform built for high-volume attraction, tour, and activity operators, covering online, in-person, and third-party sales. Operators on the platform include the Empire State Building, Tower Bridge, the National Gallery London, 360 CHICAGO, Berlin TV Tower, Up at The O2, Moco Museum, Paramount Studio Tours, the Pilsner Urquell Experience, Big Bus Tours, Tootbus, Historic Tours of America, Boston Duck Tours, Uber Boat by Thames Clippers, and Gray Line and City Sightseeing operators.

Major resellers including Viator, GetYourGuide, Expedia, Groupon, Klook, Headout, Go City, TUI Musement, and Tiqets have already integrated.

{% content-ref url="/pages/QCgnfmcQ1vc9zlYM9SlX" %}
[Ventrata Clients](/additional-resources/ventrata-clients.md)
{% endcontent-ref %}

Learn more about Ventrata at [ventrata.com](https://ventrata.com/).

## Start here

{% content-ref url="/pages/tETNJrFtVnDebo5bzZ3B" %}
[Steps to Integrate](/getting-started/steps-to-integrate.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M9NSmeseClnubIibLpV" %}
[Test Credentials](/getting-started/test-credentials.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M93No\_K9aJgc82a5wXn" %}
[Authentication](/getting-started/getting-started.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M94SNzV1D0P2QS8KHiR" %}
[Endpoints & Capabilities](/getting-started/request-capabilities.md)
{% endcontent-ref %}

## Certification and terms

We certify your integration before listing you, and a supplier can only issue you credentials once you are listed. The Partner Terms apply to every partner; the API Terms apply on top if you use our API.

{% content-ref url="/pages/O0TC8UKCmgwQpG0q09dI" %}
[Partner Terms](/partner-terms.md)
{% endcontent-ref %}

{% content-ref url="/pages/y5TduA1dKLVH0CKh172A" %}
[API Terms](/api-terms.md)
{% endcontent-ref %}

## Support

Write to <connectivity@ventrata.com> with integration questions — typical response time is one to two business days. For active integrations we can set up a shared Slack or Teams channel.

{% content-ref url="/pages/-MLCBYITnkZyqPDaMAkY" %}
[FAQs](/additional-resources/faqs.md)
{% endcontent-ref %}

{% content-ref url="/pages/vdARKulrCR8J8n0HRGq8" %}
[Support](/additional-resources/support.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ventrata.com/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
