Skip to main content

Reservotron: Operator Backend

Connect Reservotron to Ventrata to resell Reservotron operators' products with live availability and bookings.

Reservotron logo

 

Reservotron is a Quebec booking platform for tourism businesses that combine lodging, activities and equipment rental in one operation, sold in French and English. It is built for operators with detailed inventory spread across several properties and sales channels, with online and in-person bookings, automated guest emails and customer records, and connects lodging inventory to hotel OTAs through a channel manager.

 

Connecting Reservotron to Ventrata lets you resell products from operators that use Reservotron as their booking system. Ventrata reads their live availability from Reservotron, and every booking you take is created directly in the operator's Reservotron account.

 

To learn more about Reservotron, visit reservotron.com.

 

Primary website

Tags

Booking / Ticketing System

Connection features

Availability Sync · Bookings Sync

Developed by

Ventrata (using Reservotron OCTO API)

 

This operator connection (also called a backend) lets you resell products from operators that use Reservotron as their primary booking system, with every booking created directly in Reservotron. Features of this connection include:

  • Availability Sync – live availability comes from the operator's Reservotron account.

  • Bookings Sync – bookings, updates and cancellations post from Ventrata to Reservotron, and Reservotron issues the tickets or vouchers.

 

Creating the Reservotron Connection

🔐 Required Role Permissions: See Operators, Modify Operators, See Products, Modify Products

Before you begin:

  • You must have a commercial agreement with the operator for their rates and terms.

  • You must have the OCTO API Key and OCTO Endpoint for the operator. See the steps below.

  • The company whose products you want to resell is created as an operator in Ventrata.

  • The operator's products are created in Ventrata. The connection syncs availability, pricing and bookings but does not create products.

  • You must recreate the operator's products in Ventrata. See how to create products. The connection syncs availability, pricing and bookings, but doesn't create products in Ventrata.

 

Step 1: Configure the Operator in Ventrata

Ask the operator that uses Reservotron for both. The operator can contact the Reservotron team for help obtaining them.

 

  1. In the Ventrata Dashboard, go to Products → Operators and open the operator. If they don't exist yet, create them as an operator first.

  2. In the Backend Partner section, select Reservotron and enter the OCTO API Key and OCTO Endpoint. Reservotron provides a unique endpoint for each operator, in the format https://reservotron.com/octo/api/v1/.

  3. Choose Reservotron in the Backend Partner section of the operator.

  4. Enter the OCTO API Key and OCTO Endpoint, then click Update Operator.

  5. Press Update Operator.

 

 

 

📒 NOTE – Each OCTO API Key and OCTO Endpoint connects you to one operator. Set up each Reservotron operator separately.

 

Step 2: Connect Each Product

  1. Open the operator's product in Products → Products and edit it. Check that Operator is set to this operator.

  2. Tick Backend Connected. Tick Backend Availability to use availability from Reservotron.

  3. Press Update Product.

📒 NOTE

When you use Backend Pricing, net (wholesale) prices returned by Reservotron are recorded as your cost price, whatever cost percentage is set on the operator.

 

Set the product's Operator to the operator with the Reservotron backend, check Backend Connected, then Backend Availability and/or Backend Pricing. Without them, the product uses availability/pricing set in Ventrata but still posts bookings to Reservotron.

 

Check Backend Connected for this product to use the API connection (backend). To pull availability from Reservotron, ensure Backend Availability is checked; to pull pricing, check Backend Pricing. If you do not check Backend Availability and/or Backend Pricing, the product will use the availability and/or pricing configured in Ventrata but will still post bookings to Reservotron. Click Update Product to save.

 

Mapping Products to Reservotron

‼️ IMPORTANT

Mapping tells Ventrata which Reservotron product, option and units to check availability for and book. If a backend-connected product isn't mapped correctly, its bookings fail. A red highlight across the product row shows an incorrectly mapped product.

 

  1. In the Ventrata Dashboard, go to Products → Products and open the product.

  2. Open the Mappings tab. It appears once the product is set to Backend Connected.

  3. For each Ventrata option and unit, select the matching Reservotron product, option and units from the dropdowns, which Ventrata loads from Reservotron. Don't leave any field empty.

  4. Press Save Changes.

 

The product page will now display a Mappings tab. Navigate to this tab and map your Ventrata product, option(s), and units by selecting the corresponding products, options, and units from the dropdown lists as received from Reservotron. Ensure that no fields are left empty (unmapped), and click Save Changes.

 

📗 TIP

Make a test booking after mapping, and ask the operator to confirm it arrived in their Reservotron account.

 

Managing the Reservotron Connection

  • Update the mapping when the operator changes products, options or units in Reservotron.

  • Replace the key on the operator if Reservotron or the operator issues a new one.

  • Switch Backend Availability or Backend Pricing off on a product to use Ventrata's own availability or prices instead. Bookings still post to Reservotron.

 

Connection Features Detailed

This section is for anyone who wants to know exactly how the Reservotron connection works. Here the direction is the opposite of a reseller connection: Ventrata calls Reservotron, using Reservotron OCTO API. For each feature, it explains which calls Ventrata makes, when, and what that means for you.

 

In short: Ventrata asks Reservotron for availability whenever someone looks at a backend-connected product, and creates every booking in the operator's Reservotron account. Reservotron doesn't send changes back to Ventrata.

 

Timings are typical for Reservotron and rounded, and they can change.

 

Product Mapping

✅

You map each Ventrata product, option and unit to the operator's Reservotron product in the Ventrata Dashboard.

This works as follows:

  • Get Products (GET /products) – Ventrata reads the operator's Reservotron products, options and units to fill the dropdowns on the Mappings tab.

 

What this means for you: if something is missing from the dropdown, the operator hasn't made it available to you in Reservotron. Ask them to.

Content Sync

❌

Ventrata doesn't import product content from Reservotron.

Ventrata doesn't import product content from Reservotron. You create and describe the products in Ventrata yourself.

Availability Sync

✅

With Backend Availability on, Ventrata checks the operator's live availability in Reservotron.

This works as follows:

  • Availability Check (POST /availability) – when someone uses the availability calendar in Ventrata, for example in the Dashboard, your web checkout or a terminal, Ventrata asks Reservotron live for the dates on screen.

  • With Backend Availability on, Ventrata makes a live OCTO availability request to Reservotron when a user interacts with the calendar (dashboard, web checkout, terminal, etc.), usually in 7-day ranges or for a specific day. The calendar may show cached (non-live) data from the previous request before the user interacts.

 

What this means for you: customers book against the operator's live Reservotron availability, so you can't oversell a slot the operator has already sold elsewhere.

Pricing Sync

❌

Ventrata doesn't read prices from Reservotron.

Ventrata doesn't read prices from Reservotron. Products use the prices you set in Ventrata, and bookings still post to Reservotron.

When you use Backend Pricing, net (wholesale) prices returned by Reservotron are recorded as your cost price, whatever cost percentage is set on the operator.

Promotions Sync

❌

Promotions aren't sent to Reservotron.

Promotions aren't sent to Reservotron. Your Ventrata promotions still apply to the price your customer pays in Ventrata.

Bookings Sync

✅

Bookings made in Ventrata for a backend-connected product are created in the operator's Reservotron account.

This works as follows:

  1. Hold: Booking Reservation (POST /bookings) – when the product is added to the cart in Ventrata, Ventrata reserves the places in Reservotron.

  2. Confirm: Booking Confirmation (POST /bookings/{uuid}/confirm) – after payment, Ventrata confirms the booking in Reservotron with the customer's contact details, and the ticket or voucher Reservotron returns becomes the Ventrata ticket or voucher.

  3. Change: Booking Update (PATCH /bookings/{uuid}) – changes made in Ventrata are sent to Reservotron.

  4. Cancel: Booking Cancellation (POST /bookings/{uuid}/cancel) – cancellations made in Ventrata are sent to Reservotron.

Bookings, changes and cancellations for Backend Connected products are sent to Reservotron automatically: reservation when the product is added to the cart, confirmation after payment (with customer contact info), update when a booking changes, cancel when a booking is cancelled. The voucher/ticket from Reservotron is ingested in Ventrata, except PDF_FILE, which Ventrata does not support.

 

‼️ IMPORTANT – Bookings sync one way, from Ventrata to Reservotron. If the operator changes or cancels a booking in Reservotron, Ventrata isn't notified. Ask the operator to tell you about any changes they make.

Pickups/Dropoff Sync

❌

Pickup and drop-off details aren't passed to Reservotron.

Pickup and drop-off details aren't passed to Reservotron. Share them with the operator another way if a product needs them.

Custom Questions Sync

❌

Answers to your booking questions aren't passed to Reservotron.

Answers to your booking questions aren't passed to Reservotron. Share them with the operator another way if they need them.

Extras Sync

❌

Extras and add-ons aren't booked in Reservotron.

Extras and add-ons aren't booked in Reservotron. Only the main product, option and units are.

Redemption Sync

❌

Redemptions and other status changes in Reservotron aren't sent back to Ventrata after a booking is confirmed.

Redemptions and other status changes in Reservotron aren't sent back to Ventrata after a booking is confirmed.

Not supported. Booking status from Reservotron (for example Redeemed) is not communicated back to Ventrata after confirmation.

Pass Walkup Scanning Sync

❌

Pass walk-up scanning isn't available with Reservotron.

Pass walk-up scanning isn't available with Reservotron.

Gift Card Sync

❌

Ventrata gift cards aren't passed to Reservotron.

Ventrata gift cards aren't passed to Reservotron. Gift card payments stay in Ventrata.

✅ supported · ❌ not supported

 

Good to know: limits and details of the Reservotron connection

  • Live availability: availability comes from Reservotron as people browse.

  • One-way bookings: changes the operator makes in Reservotron don't reach Ventrata.

  • Reservotron is online booking software for tourism, developed and managed by Code Génome, popular with operators in Quebec, Canada.

 

FAQs

I get an error when I save the operator's backend configuration.

The OCTO API Key and OCTO Endpoint or endpoint is most likely incorrect. Check them with your operator. If the issue persists, contact our Technical Support.

There's no Backend Connected box in the product settings.

The operator set on the product most likely doesn't have a backend configured. Check the operator's Backend Partner settings and try again. If the issue persists, contact our Technical Support.

The product, option or unit I want to map isn't in the dropdown.

The dropdowns list what the operator has made available to you in Reservotron. Ask the operator. If the issue persists, contact our Technical Support.

Bookings fail for a backend-connected product.

Check the product's mapping first: every option and unit must be mapped. Then check that the slot is still available in Reservotron. If the issue persists, contact our Technical Support.

Error when updating the operator to save the backend configuration.

Likely the OCTO API Key or OCTO Endpoint is incorrect. Double-check these details with your operator. If the issue persists, contact Ventrata support.

The product/option/unit I want to map is not in the dropdown.

The dropdown list is pulled from Reservotron based on the products, options and units the operator made available to you. Double-check these details with your operator. If the issue persists, contact Ventrata support.

 

Useful Resources

 

 

Partner Information

Code Genome Inc. d/b/a Reservotron

400 Av. Atlantic #205

Outremont, QC H2V 1A5, Canada

 

Ventrata Partner ID: 946d0506-4ab3-4fa9-a701-06e85519f7a2

Did this answer your question?