Skip to main content

Smartvisit: Reseller Connection

Connect Smartvisit to Ventrata to sync availability and receive bookings instantly. Prepaid digital destination passes.

Smartvisit logo

 

Smartvisit builds digital city and destination passes, packaging attractions, tours, dining and shopping into app-based products with ticketless redemption and geolocated audio itineraries, for destination marketing organizations, hotels and loyalty programs. For operators, it brings travelers who have already prepaid a destination bundle and pick venues from the app once in town, incremental visits routed from the pass issuer's own channels, with attractions and tours the core content.

 

Connecting Smartvisit to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically.

 

To learn more about partnering with Smartvisit, visit smartvisit.com.

 

📒 NOTE

Looking to resell products from operators that use Smartvisit instead? See Smartvisit: Operator Backend.

 

Primary website

Tags

Multi-Attraction Pass

Destination markets

🌎 Global

Source markets

🌎 Global

Specialties

Prepaid digital destination passes

Connection features

Availability Sync · Bookings Sync

Ventrata Booked GMV (last 12 months)

US$10k+

Ventrata Booked Suppliers (last 12 months)

5+

Developed by

Smartvisit (using Ventrata's OCTO API)

 

This reseller connection lets you sell your products through Smartvisit without managing availability and bookings by hand. Features of this connection include:

  • Availability Sync – Smartvisit checks your live availability in Ventrata.

  • Bookings Sync – bookings, updates and cancellations from Smartvisit are created in Ventrata instantly, and customers get Ventrata tickets.

 

Creating the Smartvisit Connection

🔐 Required Role Permissions: See Connections, Modify Connections, See Connection Key

Before you begin:

  • You must have a commercial agreement with Smartvisit for them to sell your products. To inquire about partnering with them, contact them via smartvisit.com.

  • You must have Smartvisit created as a Reseller in Ventrata with their pricing (retail, wholesale/commission) defined correctly. Note that this API connection requires that the reseller is set to the "Bill to my account" settlement method.

 

  1. In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Smartvisit from the list of partners.

  2. Select Smartvisit Reseller from the list of your resellers (must be created before creating a connection). The connection will inherit the reseller's configuration like pricing, allowed destinations, products, etc.

  3. (Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Smartvisit connections and would like to differentiate between them more easily in the future.

  4. Press the Create Octo Connection button.

 

📗 TIP

If needed, you can also allow or disallow products or destinations on the connection level, in addition to what you have configured on the reseller.

 

Mapping Products to Smartvisit

Securely share the OCTO API key shown on the connection you've created with your Smartvisit contact and ask them to map your products using Ventrata's OCTO API, with pricing (octo/pricing) enabled. Typically, it takes no longer than a few business days for the Smartvisit team to complete this.

 

Your Ventrata configuration is complete. You do not need to take any further steps.

 

📗 TIP

Smartvisit can access all products enabled on the connection, but you can also provide the Product and Option IDs from the connection page when contacting them to specify what to map.

 

 

Managing the Smartvisit Connection

  • Allow or disallow products: limit which destinations, products and options Smartvisit can access. See how to allow or disallow products.

  • Rename the connection to tell several Smartvisit connections apart.

 

Connection Features Detailed

This section is for anyone who wants to know exactly how the Smartvisit connection works: which Ventrata OCTO API calls Smartvisit makes, when it makes them, and what that means for you. Each call links to Ventrata's API documentation.

 

In short: Smartvisit pulls everything it needs from Ventrata. It reads your products, checks your availability (and your prices, when it asks for them), and sends bookings and cancellations. Ventrata doesn't push changes to Smartvisit, so anything you change in Ventrata reaches Smartvisit the next time it checks.

 

Timings are typical for Smartvisit and rounded, and they can change if Smartvisit changes how it syncs.

 

Product Mapping

❌

You can't map products from Ventrata. Smartvisit maps them on its side, through your account manager or Smartvisit's portal.

This works as follows:

  • Get Products (GET /products) – when Smartvisit sets up your connection, and whenever it refreshes its listings, it reads every product enabled on the connection, with its options and units (ticket types such as Adult or Child).

  • Get Product (GET /products/{productId}) – Smartvisit re-reads a single product to pick up changes to its options, units, booking cutoffs and settings.

  • Mapping on Smartvisit's side – Smartvisit links each Ventrata option and unit to its own listing and ticket types. Your Smartvisit account manager does this for you, or you do it in Smartvisit's own portal if Smartvisit offers one. You only share the connection's API key.

 

What this means for you: Smartvisit can only sell what it has mapped. When you add a product, option or unit in Ventrata, Smartvisit may see it on its next refresh, but it won't sell it until it's mapped. So tell your Smartvisit account manager whenever you add one.

Content Sync

❌

Smartvisit doesn't read your product content from Ventrata.

Smartvisit uses the descriptions, images and other content set up on its own side, so update your content with Smartvisit directly.

Availability Sync

✅

Smartvisit checks your live availability in Ventrata. Ventrata doesn't push availability changes to Smartvisit.

This works as follows:

  • Availability Check (POST /availability) – Smartvisit sends a product, an option and a date or date range. Ventrata answers with each bookable day or time slot, its status (AVAILABLE, LIMITED, SOLD_OUT, CLOSED or FREESALE), the remaining vacancies, the booking cutoff and an availabilityId, which Smartvisit needs to book that slot.

  • Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Smartvisit can't overbook a slot that has just sold out, even if its stored availability is slightly out of date.

 

Typically with Smartvisit:

  • Availability Check: Smartvisit checks your products throughout the day and re-checks the same product and dates about every 8 hours.

 

What this means for you: when you close a date, change capacity or sell out in Ventrata, Smartvisit shows it after its next check. For dates it checks regularly, that's within about 8 hours. Dates further ahead are usually checked less often.

Pricing Sync

❌

Smartvisit doesn't get your prices from Ventrata.

Prices on Smartvisit are managed on Smartvisit's side, so keep them up to date with Smartvisit directly.

Promotions Sync

❌

Your Ventrata promotions don't apply on Smartvisit.

Prices on Smartvisit don't include promotions you create in Ventrata. Set up any promotions with Smartvisit directly.

Bookings Sync

✅

Bookings and cancellations made on Smartvisit are created in Ventrata instantly, and customers get Ventrata tickets.

This works as follows:

  1. Hold: Booking Reservation (POST /bookings) – when a customer starts checkout on Smartvisit, Smartvisit sends the product, option, chosen slot (availabilityId) and one unit item per person. Ventrata checks capacity again and creates an ON_HOLD booking, which holds the places while the customer pays. If there's no longer room, Ventrata rejects the hold.

  2. Confirm: Booking Confirmation (POST /bookings/{uuid}/confirm) – once payment goes through, Smartvisit confirms the hold, with its own booking reference and the customer's contact details. The booking becomes CONFIRMED in Ventrata, and Ventrata sends back your booking reference and the tickets (one per person) or a voucher (one per booking), depending on how your product is set up, each with a QR code and a PDF link. Smartvisit gives these to the customer, who shows them at your entrance like any Ventrata ticket.

  3. Expire: if the customer doesn't finish paying, Smartvisit never confirms, and the hold expires on its own and frees the places.

  4. Cancel: Booking Cancellation (POST /bookings/{uuid}/cancel) – when a customer cancels on Smartvisit, Smartvisit cancels the booking in Ventrata. Ventrata accepts this only if the booking can still be cancelled and the option's cancellation cutoff hasn't passed. Otherwise it rejects the request, and Smartvisit has to contact you.

  5. Change: Smartvisit doesn't use Booking Update (PATCH /bookings/{uuid}), so a change most likely reaches Ventrata as a cancellation plus a new booking.

 

Typically with Smartvisit:

  • Smartvisit doesn't set a hold time, so the default hold time applies.

  • A typical Smartvisit booking is for about 2 people.

  • Smartvisit also checks the bookings it has made, with Get Booking (GET /bookings/{uuid}) every few minutes, for example to reconcile its records.

 

‼️ IMPORTANT – Bookings sync one way, from Smartvisit to Ventrata. If you cancel, change or rebook a booking from Smartvisit in Ventrata, for example in the Dashboard, Smartvisit isn't notified. Contact Smartvisit so the booking is cancelled or changed on their side too, or ask the customer to cancel through Smartvisit.

Pickups/Dropoff Sync

❌

Smartvisit doesn't send pickup or drop-off details with its bookings.

If your products include pickups, check with Smartvisit how it collects pickup details, or arrange them with the customer.

Custom Questions Sync

✅ / ❌

Smartvisit sends answers to your booking questions with its bookings.

This works as follows:

  • octo/questions capability – Smartvisit reads the questions set on your products and sends the customer's answers with the booking, where you see them in Ventrata.

 

Typically with Smartvisit:

  • Smartvisit sends answers to your booking questions.

Extras Sync

❌

Extras and add-ons can't be booked through Smartvisit.

Customers can only book your main products and options on Smartvisit. Sell extras separately, for example on arrival.

Redemption Sync

❌

Redemptions aren't reported to Smartvisit.

Ventrata doesn't notify Smartvisit when a ticket is scanned or redeemed. Smartvisit only sees a redemption if it reads the booking back from Ventrata.

Pass Walkup Scanning Sync

❌

Smartvisit pass holders can't be scanned at your entrance without a booking.

Customers from Smartvisit need a booking made through Smartvisit before they visit.

Gift Card Sync

❌

Ventrata gift cards can't be sold or redeemed through Smartvisit.

Gift cards bought in Ventrata can't be used on Smartvisit, and Smartvisit can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

 

Good to know: limits and details of the Smartvisit connection

  • Delays: availability and prices reach Smartvisit only when it checks, so there's always a short delay after you change something in Ventrata.

  • Cancellation cutoff: Smartvisit can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.

  • What Smartvisit can see: only the destinations, products and options allowed on the reseller and the connection, and enabled for sale on the Direct API source. See how to allow or disallow products.

  • Tickets: Smartvisit issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.

  • Test bookings: Smartvisit can send test bookings while it sets up the connection. Test bookings don't use your availability and aren't invoiced.

 

FAQs

No products are displayed on the connection page.

Verify which destinations, products, and options are allowed on your reseller and connection. Next, confirm that your products and options are enabled for sale on the Direct API source. If the issue persists, contact our Technical Support.

My Ventrata products use Booking Size fares, and pricing isn't working correctly on Smartvisit.

After every fare change, update the product mapping to ensure the partner tier counts are synced with Ventrata. Ensure the fare is enabled for sale over Direct API.

 

 

Partner Information

Smartvisit International Pty Ltd

PO Box 553, Kiama Downs, NSW

Australia

 

Ventrata Partner ID: 8403fed5-cc6c-4dcb-9a84-6169d04f7ef4

Did this answer your question?