TourDesk is a tour and activity sales system for accommodation providers, founded in 2013, putting local inventory in front of hotel, hostel and guesthouse guests through a front-desk agent system and a guest-facing online portal run by the property. For operators, it brings in-destination demand from guests already checked in or about to arrive, booking day tours, excursions and transfers at the reception desk or from the property's portal, densest in Iceland and Ireland and with Radisson Blu among its properties.

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

To learn more about partnering with TourDesk, visit tourdesk.com.

Primary website	tourdesk.com
Tags	Hotel & Concierge Channel
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Front-desk sales to hotel and hostel guests
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Ventrata Booked Suppliers (last 12 months)	5+
Developed by	TourDesk (using Ventrata's OCTO API)

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

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

Creating the TourDesk Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the TourDesk connection

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

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

Tour Desk ehf.

Laugavegur 3, 101 Reykjavík

Iceland

tourdesk.com

Ventrata Partner ID: b11cd20e-9afa-4629-a7f2-21ef84a9d982

TourDesk: Reseller Connection