Experienza, formerly Tuexperiencia, is a B2B marketplace for excursions, guided tours and activities, selling to travel agents, distributors and resellers through an API, B2B portal, white-label sites and connectors to marketplaces and channel managers. It carries over 4,000 products across 70 countries and 300 destinations, with offices in Madrid and Mexico City and teams in Bogotá, Buenos Aires, Cancún, Palma and Barcelona. For operators, it brings trade demand only, Spanish and Latin American travel agencies and resellers packaging tours and activities for their leisure clients, with no consumer storefront.

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

To learn more about partnering with Experienza, visit experienza.travel.

Primary website	experienza.travel
Tags	OTA · Tours & Activities OTA · B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	B2B excursions and activities for travel agents and resellers
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Ventrata Booked Suppliers (last 12 months)	10+
Developed by	Prioticket (using Ventrata's OCTO API)

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

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

Creating the Experienza Connection

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

Before you begin:

You must have a commercial agreement with Experienza for them to sell your products. To inquire about partnering with them, contact them via experienza.travel.
You must have Experienza 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 Experienza (powered by Prioticket) from the list of partners.
Select Experienza 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 Experienza 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 Experienza

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

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

📗 TIP

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

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

Connection Features Detailed

This section is for anyone who wants to know exactly how the Experienza connection works: which Ventrata OCTO API calls Experienza 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: Experienza 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 Experienza, so anything you change in Ventrata reaches Experienza the next time it checks.

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

Product Mapping	❌	You can't map products from Ventrata. Experienza maps them on its side, through your account manager or Experienza's portal. This works as follows: Get Products (`GET /products`) – when Experienza 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}`) – Experienza re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Experienza's side – Experienza links each Ventrata option and unit to its own listing and ticket types. Your Experienza account manager does this for you, or you do it in Experienza's own portal if Experienza offers one. You only share the connection's API key. Typically with Experienza: Experienza reads your full product list every few days. It re-reads each product about every 2 hours. What this means for you: Experienza can only sell what it has mapped. When you add a product, option or unit in Ventrata, Experienza may see it on its next refresh, but it won't sell it until it's mapped. So tell your Experienza account manager whenever you add one.
Content Sync	✅ / ❌	Experienza can read your product content, such as descriptions and images, from Ventrata. This works as follows: `octo/content` capability – when Experienza 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 Experienza on its next product refresh. Typically with Experienza: Experienza requests `octo/content`.
Availability Sync	✅	Experienza checks your live availability in Ventrata. Ventrata doesn't push availability changes to Experienza. This works as follows: Availability Check (`POST /availability`) – Experienza 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 Experienza needs to book that slot. Availability Calendar (`POST /availability/calendar`) – returns one summary per day instead of every time slot, typically to show which dates are open in a date picker. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Experienza can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Experienza: Availability Check: Experienza checks each product about every 5 hours, usually starting about 3 months ahead and covering 27 days per request and looks up to about a year ahead. Availability Calendar: Experienza checks each product about every 9 hours, usually starting tomorrow and covering about 6 months per request and looks up to about 6 months ahead. Checks are spread through the day with no strong peak, which suggests a mix of scheduled syncs and live customer searches. What this means for you: when you close a date, change capacity or sell out in Ventrata, Experienza shows it after its next check. For dates it checks regularly, that's within about 5 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅ / ❌	Your prices come back with availability only when Experienza asks for them, and Experienza doesn't always do so. This works as follows: `octo/pricing` capability – Experienza 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 Experienza, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Experienza 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 Experienza: Experienza requests `octo/pricing` on only part of its availability checks, so not every listing may use your Ventrata prices. Experienza 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 Experienza. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Experienza to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Experienza's portal. Otherwise it may be off, and Experienza won't receive your Ventrata prices.
Promotions Sync	❌	Your Ventrata promotions don't apply on Experienza. Prices on Experienza don't include promotions you create in Ventrata. Set up any promotions with Experienza directly.
Bookings Sync	✅	Bookings and cancellations made on Experienza 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 Experienza, Experienza 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, Experienza 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. Experienza gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Experienza 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 Experienza, Experienza 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 Experienza has to contact you. Change: Experienza doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Experienza: Experienza holds places for about 60 minutes while the customer pays (`expirationMinutes`). A typical Experienza booking is for about 1 person. 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 Experienza to Ventrata. If you cancel, change or rebook a booking from Experienza in Ventrata, for example in the Dashboard, Experienza isn't notified. Contact Experienza so the booking is cancelled or changed on their side too, or ask the customer to cancel through Experienza.
Pickups/Dropoff Sync	❌	Experienza doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Experienza how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Experienza doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Experienza how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Experienza. Customers can only book your main products and options on Experienza. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Experienza. Ventrata doesn't notify Experienza when a ticket is scanned or redeemed. Experienza only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Experienza pass holders can't be scanned at your entrance without a booking. Customers from Experienza need a booking made through Experienza before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Experienza. Gift cards bought in Ventrata can't be used on Experienza, and Experienza can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Experienza connection

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

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

Are You Experienced SL

C/ Alonso Cano 66

28003 Madrid, Spain

experienza.travel

Ventrata Partner ID: 4c3ba5df-1e01-477f-96bf-9bea19bf607e

Prioticket B.V.

Prins Hendrikkade 21

1012 TL Amsterdam, Netherlands

prioticket.com

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

Experienza: Reseller Connection