# Steps to Integrate

{% hint style="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 <connectivity@ventrata.com>.
{% endhint %}

{% stepper %}
{% step %}

### 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](/getting-started/request-capabilities.md) you will implement. Ventrata requires all resellers to support OCTO core endpoints as a minimum:

* [Products](/octo-core/products.md)
* [Availability](/octo-core/availability.md)
* [Booking](/octo-core/bookings.md)

Implementing capabilities is optional, but Ventrata strongly recommends at least [Pricing](/capabilities/pricing.md), because dynamic pricing is now widely used by [Ventrata clients](/additional-resources/ventrata-clients.md).

Contact us if you have implementation questions or want to discuss specific capabilities.
{% endstep %}

{% step %}

### 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](/getting-started/test-credentials.md).

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](/getting-started/test-credentials.md) for access.
{% endstep %}

{% step %}

### Step 3: Test

After self-testing your implementation with EdinExplore, contact <connectivity@ventrata.com> for integration review and approval. We will also require your company name, a logo, a favicon, a short, supplier facing description and a link to your website for your listing on Ventrata.

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.
{% endstep %}

{% step %}

### Step 4: Go Live

After approval, your integration is added to Ventrata's partner list and documented in our [helpdesk](https://ventrata.crisp.help/en/category/connectivity-1dqf093/), so suppliers can enable it and share API keys with your team.

At that point, you can contact [Ventrata clients](/additional-resources/ventrata-clients.md) to connect products and begin selling.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ventrata.com/getting-started/steps-to-integrate.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.