Xplorie is a US activity program for vacation rental brands, bundling admission to local tours and attractions into guest stays at no cost to the guest, so lodging partners use activities as a marketing asset. For operators, it brings pre-committed redemption demand from the guests of around 170 lodging partners, about three million guests a year in US vacation markets who have chosen their activity before arrival, through a program working with hospitality brands since 1996.

Connecting Xplorie to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically. Xplorie runs on Prioticket, and receives your products through its certified integration with Ventrata's OCTO API.

To learn more about partnering with Xplorie, visit xplorie.com.

Primary website	xplorie.com
Tags	B2B Marketplace · Hotel & Concierge Channel
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Activities bundled into vacation rental stays
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Prioticket (using Ventrata's OCTO API)

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

Availability Sync – Xplorie checks your live availability in Ventrata.
Pricing Sync – Xplorie gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Xplorie are created in Ventrata instantly, and customers get Ventrata tickets.

Creating the Xplorie Connection

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

Before you begin:

You must have a commercial agreement with Xplorie for them to sell your products. To inquire about partnering with them, contact them via xplorie.com.
You must have Xplorie 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.

In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Xplorie (powered by Prioticket) from the list of partners.
Select Xplorie 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.
(Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Xplorie connections and would like to differentiate between them more easily in the future.
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 Xplorie

Securely share the OCTO API key shown on the connection you've created with your Xplorie 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 Xplorie team to complete this.

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

📗 TIP

Xplorie 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 Xplorie Connection

Allow or disallow products: limit which destinations, products and options Xplorie can access. See how to allow or disallow products.
Rename the connection to tell several Xplorie connections apart.

Connection Features Detailed

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

In short: Xplorie 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 Xplorie, so anything you change in Ventrata reaches Xplorie the next time it checks.

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

Product Mapping	❌	You can't map products from Ventrata. Xplorie maps them on its side, through your account manager or Xplorie's portal. This works as follows: Get Products (`GET /products`) – when Xplorie 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}`) – Xplorie re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Xplorie's side – Xplorie links each Ventrata option and unit to its own listing and ticket types. Your Xplorie account manager does this for you, or you do it in Xplorie's own portal if Xplorie offers one. You only share the connection's API key. Typically with Xplorie: Xplorie reads your full product list about once a day. What this means for you: Xplorie can only sell what it has mapped. When you add a product, option or unit in Ventrata, Xplorie may see it on its next refresh, but it won't sell it until it's mapped. So tell your Xplorie account manager whenever you add one.
Content Sync	✅ / ❌	Xplorie can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Xplorie adds it to the `Octo-Capabilities` header, Get Products (`GET /products`) and Get Product (`GET /products/{productId}`) also return your product content, such as descriptions, highlights, inclusions and images. Content changes in Ventrata reach Xplorie on its next product refresh. Typically with Xplorie: Xplorie requests `octo/content`.
Availability Sync	✅	Xplorie checks your live availability in Ventrata. Ventrata doesn't push availability changes to Xplorie. This works as follows: Availability Check (`POST /availability`) – Xplorie 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 Xplorie needs to book that slot. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Xplorie can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Xplorie: Availability Check: Xplorie checks your products throughout the day, usually starting about 3 months ahead and covering 30 days per request, looks up to about a year ahead and re-checks the same product and dates about every 19 hours. Checks are busiest between 16:00 and 22:00 UTC, which suggests most checks are live, as customers browse Xplorie. What this means for you: when you close a date, change capacity or sell out in Ventrata, Xplorie shows it after its next check. For dates it checks regularly, that's within about 19 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅ / ❌	Your prices come back with availability only when Xplorie asks for them, and Xplorie doesn't always do so. This works as follows: `octo/pricing` capability – Xplorie asks for prices by adding `octo/pricing` to the `Octo-Capabilities` header of its requests. Without it, Ventrata sends availability with no prices at all. Availability Check (`POST /availability`) – with pricing on, each day or time slot comes back with your price per unit (ticket type): the retail price the customer pays and the net price you invoice Xplorie, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Xplorie also sends how many people of each unit type are booking, Ventrata prices that exact group. This matters for Booking Size fares and other group pricing. Booking Reservation (`POST /bookings`) and Booking Confirmation (`POST /bookings/{uuid}/confirm`) – the booking comes back with its final retail and net price, so the booking in Ventrata always records the price it was sold at. Typically with Xplorie: Xplorie requests `octo/pricing` on only part of its availability checks, so not every listing may use your Ventrata prices. Xplorie doesn't send the number of people per unit type, so prices come back per person, and group pricing such as Booking Size fares may not show correctly on Xplorie. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Xplorie to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Xplorie's portal. Otherwise it may be off, and Xplorie won't receive your Ventrata prices.
Promotions Sync	✅ / ❌	Your Ventrata promotions can apply to Xplorie prices and bookings. This works as follows: `octo/offers` capability – with it, Ventrata applies your eligible promotions to availability prices and to bookings, and Xplorie can also send a promo code (`offerCode`). Promotions work together with pricing, so they need `octo/pricing` as well. This covers promotions you create in Ventrata (supplier-initiated promotions). Typically with Xplorie: Xplorie requests `octo/offers`.
Bookings Sync	✅	Bookings and cancellations made on Xplorie are created in Ventrata instantly, and customers get Ventrata tickets. This works as follows: Hold: Booking Reservation (`POST /bookings`) – when a customer starts checkout on Xplorie, Xplorie 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. Confirm: Booking Confirmation (`POST /bookings/{uuid}/confirm`) – once payment goes through, Xplorie 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. Xplorie gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Xplorie never confirms, and the hold expires on its own and frees the places. Cancel: Booking Cancellation (`POST /bookings/{uuid}/cancel`) – when a customer cancels on Xplorie, Xplorie 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 Xplorie has to contact you. Change: Xplorie doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Xplorie: Xplorie holds places for about 60 minutes while the customer pays (`expirationMinutes`). A typical Xplorie booking is for about 4 people. It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire. ‼️ IMPORTANT – Bookings sync one way, from Xplorie to Ventrata. If you cancel, change or rebook a booking from Xplorie in Ventrata, for example in the Dashboard, Xplorie isn't notified. Contact Xplorie so the booking is cancelled or changed on their side too, or ask the customer to cancel through Xplorie.
Pickups/Dropoff Sync	❌	Xplorie doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Xplorie how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Xplorie doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Xplorie how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Xplorie. Customers can only book your main products and options on Xplorie. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Xplorie. Ventrata doesn't notify Xplorie when a ticket is scanned or redeemed. Xplorie only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Xplorie pass holders can't be scanned at your entrance without a booking. Customers from Xplorie need a booking made through Xplorie before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Xplorie. Gift cards bought in Ventrata can't be used on Xplorie, and Xplorie can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Xplorie connection

Delays: availability and prices reach Xplorie only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: Xplorie can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What Xplorie 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: Xplorie issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: Xplorie 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 Xplorie.

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.

📚 More about Ventrata connections

Partner Information

Xplorie, LLC

297 Azalea Drive

Destin, Florida 32541, USA

xplorie.com

Ventrata Partner ID: 0fe69caf-a2bc-43b2-940a-78706602a425

Prioticket B.V.

Prins Hendrikkade 21

1012 TL Amsterdam, Netherlands

prioticket.com

Ventrata Partner ID: 8347e498-1afe-48e1-9d99-8b2d1e0069fb

Xplorie: Reseller Connection