Local Experiences is a London-based online marketplace for tours and activities that resells operator inventory without running tours of its own, offering guided walks, skip-the-line tickets and short experiences across European cities including Rome, Florence, Venice, Naples, Paris, Barcelona, Lisbon and Athens, plus Dubai. For operators, it brings individual travelers and large groups booking at accessible price points in more than 20 tour languages, with gift purchases and group bookings handled alongside standard tickets.

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

To learn more about partnering with Local Experiences, visit localexperiences.tours.

Primary website	localexperiences.tours
Tags	Travel Agent
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Large groups and gift purchases at accessible price points
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Local Experiences (using Ventrata's OCTO API)

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

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

Creating the Local Experiences Connection

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

Before you begin:

You must have a commercial agreement with Local Experiences for them to sell your products. To inquire about partnering with them, contact them via localexperiences.tours.
You must have Local Experiences 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 Local Experiences from the list of partners.
Select Local Experiences 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 Local Experiences 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 Local Experiences

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

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

📗 TIP

Local Experiences 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 Local Experiences Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Local Experiences connection

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

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

LOCAL EXPERIENCES LTD

20 Wenlock Road, London, England, N1 7GU

United Kingdom

localexperiences.tours

Ventrata Partner ID: e79dc9d6-619e-4dc9-a995-09295960c72b

Local Experiences: Reseller Connection