Skip to main content

Smartvisit: Operator Backend

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

Smartvisit logo

 

Smartvisit is a destination experience platform that handles pass setup, pricing, sales and redemption for tourism operators, accommodation providers, destination marketing organizations and loyalty programs, with teams across the United States, Australia, Europe and the Gulf. Its app bundles attractions, tours, dining and shopping into branded digital passes with ticketless entry and self-guided audio trails, redeemed in real time by visitors in destination.

 

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

 

To learn more about Smartvisit, visit smartvisit.com.

 

📒 NOTE

Looking for Smartvisit to resell your products instead? See Smartvisit: Reseller Connection.

 

📗 TIP

You can allow/disallow products or destinations on the connection level, in addition to the reseller settings. This helps if you have multiple Smartvisit connections linked to one reseller.

📗 TIP

Smartvisit can access all products enabled on the connection. You can also give them the Product and Option IDs from the connection page to specify what to map.

 

Primary website

Tags

Custom / Proprietary Operator System

Connection features

Availability Sync · Bookings Sync

Developed by

Ventrata (using Smartvisit OCTO API)

 

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

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

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

 

Creating the Smartvisit 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 (shown on the connection in Ventrata) for the operator. See the steps below.

  • A commercial agreement with Smartvisit for them to sell your products.

  • Smartvisit created as a Reseller in Ventrata with retail and wholesale/commission pricing configured.

  • 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: Create Smartvisit as a reseller

Create Smartvisit as a Reseller in Ventrata with retail and wholesale/commission pricing correctly configured. The connection inherits the reseller's configuration, like pricing, allowed destinations and products.

 

Step 2: Configure the Operator in Ventrata

Ventrata generates it when you create the connection; you email it to your Smartvisit contact so they can map your products.

 

  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 Smartvisit and enter the OCTO API key (shown on the connection in Ventrata).

  3. Press Update Operator.

 

 

📒 NOTE – Each OCTO API key (shown on the connection in Ventrata) connects you to one operator. Set up each Smartvisit operator separately.

 

Step 3: 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 Smartvisit.

  3. Press Update Product.

 

Mapping Products to Smartvisit

‼️ IMPORTANT

Mapping tells Ventrata which Smartvisit 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 Smartvisit product, option and units from the dropdowns, which Ventrata loads from Smartvisit. Don't leave any field empty.

  4. Press Save Changes.

 

📗 TIP

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

 

Managing the Smartvisit Connection

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

  • Replace the key on the operator if Smartvisit 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 Smartvisit.

 

Connection Features Detailed

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

 

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

 

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

 

Product Mapping

✅

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

This works as follows:

  • Get Products (GET /products) – Ventrata reads the operator's Smartvisit 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 Smartvisit. Ask them to.

Content Sync

❌

Ventrata doesn't import product content from Smartvisit.

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

Availability Sync

✅

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

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 Smartvisit live for the dates on screen.

  • Syncs availability and pricing for your Smartvisit products with Ventrata, in real time.

 

Typically with Smartvisit:

  • Requests cover 7 days at a time, from today up to about a year ahead, as people browse and as Ventrata loads the calendar.

 

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

Pricing Sync

❌

Ventrata doesn't read prices from Smartvisit.

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

Promotions Sync

❌

Promotions aren't sent to Smartvisit.

Promotions aren't sent to Smartvisit. 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 Smartvisit 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 Smartvisit.

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

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

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

Receives bookings, updates and cancellations from Smartvisit into Ventrata.

 

‼️ IMPORTANT – Bookings sync one way, from Ventrata to Smartvisit. If the operator changes or cancels a booking in Smartvisit, 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 Smartvisit.

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

Custom Questions Sync

❌

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

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

Extras Sync

❌

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

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

Redemption Sync

❌

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

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

Pass Walkup Scanning Sync

❌

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

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

Gift Card Sync

❌

Ventrata gift cards aren't passed to Smartvisit.

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

✅ supported · ❌ not supported

 

Good to know: limits and details of the Smartvisit connection

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

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

  • Smartvisit builds digital city and destination passes (attractions, tours, dining, shopping) in app-based products with ticketless redemption and geolocated audio itineraries.

  • Works with destination marketing organisations, hotels and loyalty programs.

 

FAQs

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

The OCTO API key (shown on the connection in Ventrata) 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 Smartvisit. 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 Smartvisit. If the issue persists, contact our Technical Support.

 

Useful Resources

 

 

Partner Information

Smartvisit

Suite 202, 99 Alexander Street

Crows Nest, New South Wales 2065, Australia

 

Ventrata Partner ID: bb75947b-a65b-4f1b-af5b-d0a2f55b51b4

Did this answer your question?