VIT Travel is a destination management company (DMC) and inbound operator based in Parma, Italy, covering Italy and France and extending into Belgium, the Netherlands, Switzerland and Luxembourg, with 53 destinations in its catalog. It sells only to travel advisors and agencies through a trade portal, assembling hotels, transport and guided experiences into tailor-made cultural and culinary itineraries. For operators, it brings trade demand from agency clients on long-lead European journeys, who take private guided tours, food and wine experiences and museum visits as components of a multi-day itinerary.

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

To learn more about partnering with VIT Travel, visit vit.travel.

Primary website	vit.travel
Tags	Receptive & Inbound Operator
Destination markets	🇮🇹 Italy
Source markets	🌎 Global
Specialties	Trade-only multi-day journeys in Italy and France
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Developed by	VIT Travel (using Ventrata's OCTO API)

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

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

Creating the VIT Travel Connection

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

Before you begin:

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

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

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

📗 TIP

VIT Travel 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 VIT Travel Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the VIT Travel connection

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

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

VIT 4 Travel Srl

Via Emilia Est, 23

43121 Parma, Italy

vit.travel

Ventrata Partner ID: d3d314bc-5301-4261-ab74-2fb7cc2feaa5

VIT Travel: Reseller Connection