Booking.com is the world's largest accommodation OTA, with an attractions marketplace selling tickets and activities in more than 5,000 cities and 115 countries. For operators, it brings travelers who already hold a hotel reservation, with attraction bookings counting toward their Genius loyalty status and Booking.com providing 24/7 customer support. Direct listing is by invitation and reserved for high-volume attractions.

Connecting Booking.com to Ventrata pushes your product content, syncs your availability, prices and promotions, and delivers bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Booking.com, visit booking.com.

Primary website	booking.com/attractions
Tags	OTA · OTA with Tours & Activities Division
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Major visitor attractions and large tour operators
Connection features	Availability Sync · Pricing Sync · Promotions Sync · Bookings Sync · Content Sync
Ventrata Booked GMV (last 12 months)	US$10M+
Ventrata Booked Suppliers (last 12 months)	25+
Developed by	Booking.com (using Ventrata's OCTO API)

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

Availability Sync – Booking.com checks your live availability in Ventrata.
Pricing Sync – Booking.com gets your prices from your reseller pricing in Ventrata.
Promotions Sync – your Ventrata promotions apply on Booking.com.
Bookings Sync – bookings, updates and cancellations from Booking.com are created in Ventrata instantly, and customers get Ventrata tickets.
Content Sync – Booking.com pulls your product content from Ventrata, which must meet Booking.com’s content guidelines and minimum requirements.

Good to know

Booking.com Attractions syncs your product content from Ventrata via API. It has no interface for suppliers to manage product content manually, so check the Minimum Required Content section below.
Booking.com Attractions syncs all public promotions made available to them as a reseller on the Direct API source. Non-public promotions use the promotion code BOOKING_CLOSED_USER_GROUP. See Booking.com Promotions below.

Creating the Booking.com Connection

🔐 Required Role Permissions: See Connections, Modify Connections

Before you begin:

You must have a commercial agreement with Booking.com for them to sell your products. To start one, contact Inesa Jasarevic, Senior Account Manager at Booking.com Attractions ([email protected]).
You must have Booking.com 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.
The minimum required content information is completed for the Ventrata products you will sell on Booking.com. See Minimum Required Content below.

In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Booking.com Attractions from the list of partners.
Select Booking.com Reseller from the list of your resellers (must be created before creating a connection). The connection will inherit the reseller's (or reseller band'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 Booking.com 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 or reseller band.

Mapping Products to Booking.com

Notify your Booking.com contact that you've created the connection and ask them to map your products. Pricing Sync is always on for Booking.com, and Booking.com accesses the connection securely from Ventrata, so you don’t need to ask for pricing or share an API key or any other details. Typically, it takes no longer than a few business days for the Booking.com team to complete this.

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

📗 TIP

Booking.com 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.

Minimum Required Content

Booking.com pulls your product content from Ventrata and doesn’t offer suppliers a way to edit it on Booking.com. It checks this content against its guidelines and minimum requirements, and automatically archives products with an empty title, description or inclusions. Complete the following in your Ventrata Dashboard before you ask Booking.com to map your products.

Content	How Booking.com uses it	Where to edit in Ventrata
Supplier Address (or Destination Address, if using Destinations)	Links your product to its location on Booking.com, using its Google Place ID (or address, city, country and coordinates). A missing or outdated Place ID, including on itinerary stops, is the most common reason Booking.com doesn’t create a product or takes it offline. Use the Place ID of your exact location, not a service-area listing.	Supplier Settings → Address; Destination Settings (if using) → Address
Product Title	Used as the product name on Booking.com. There’s no separate Booking.com-only title.	Product Settings → Title (different from Internal Name)
Product Short Description	Required. 1–2 sentences, without HTML, markdown or URLs. Keep highlights out of it and use the Highlights field instead.	Product Settings → Short Description
Product Long Description	Required. Recommended length 60–120 words, without HTML, markdown or URLs.	Product Settings → Long Description
Product Gallery Images	Used on your product listing. At least 3 photos, including a cover image, following Booking.com’s photo guidelines. Add captions where you can. Booking.com syncs images by URL, so replace an image by uploading a new one rather than editing the old one.	Product Settings → Gallery Images
Product Highlights	Used on your product listing under "Unique Selling Points" without HTML, markdown, or URLs.	Product Settings → Highlights
Product Inclusions	Used on your product listing under “What’s included”. At least one inclusion is required. An item can’t be both included and excluded. No HTML, markdown or URLs.	Product Settings → Inclusions
Product Exclusions	Used on your product listing under "What's not included". Ensure no HTML, markdown, or URLs.	Product Settings → Exclusions
Product Redemption instructions	Shown to the customer after booking, before arrival, to explain how to redeem the ticket. No HTML, markdown or URLs.	Product Settings → Redemption Instructions
Product FAQs	Shown on your product listing. Every question needs an answer: a question with an empty answer stops Booking.com importing the product. No HTML, markdown or URLs.	Product Settings → FAQs
Cancellation Cutoff	Shown as your cancellation policy. The default of 0 hours shows as free cancellation until the start time. Booking.com expects 24, 48 or 72 hours, or non-refundable.	Product Settings → Cutoffs → Cancellation Cutoff
Option Title	Used on your product listing.	Option Settings → Title
Option Short Description	Used on your product listing. Must not contain any HTML, markdown, or URLs.	Option Settings → Description
Option Languages	Shown as the languages the product is offered in. Set them on every option.	Option Settings → Languages
Units (age bands)	Mapped to Booking.com ticket types. Age ranges must not overlap or leave gaps.	Option Settings → Units
Itinerary (if used)	Used on your product listing if applicable. Must not contain any HTML, markdown, or URLs.	Products → Itineraries
Voucher Template	Voucher in PDF format is issued to the customer upon booking confirmation.	Products → Templates

📗 TIP

Booking.com’s checks also flag some words, such as competitor names in titles or itineraries, and words like “weapon” in redemption instructions. Content changes usually take about 24 hours to show on Booking.com.

Booking.com Promotions

🔐 Required Role Permissions: See Promotions, Modify Promotions

Booking.com Attractions automatically syncs all public promotions made available to them as a reseller on the Direct API source.

They also support non-public promotions using the predefined promotion code BOOKING_CLOSED_USER_GROUP. If, as part of your agreement with Booking.com, you would like to offer a closed user group promotion with them, create this promotion in Ventrata, ensuring that:

The promotion is set NOT to be public.
BOOKING_CLOSED_USER_GROUP is entered in the Promotion Codes field.
The promotion is only allowed for the Booking.com Attractions reseller.

📒 NOTE

Booking.com has to be blacklisted from all active promotions (public or not) you don't want them to use.

When a booking is made on behalf of the closed user group on Booking.com, they will automatically check and apply any applicable promotions with the BOOKING_CLOSED_USER_GROUP code. Please remember promotions cannot be combined.

Managing the Booking.com Connection

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

Connection Features Detailed

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

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

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

Product Mapping	❌	You can't map products from Ventrata. Booking.com maps them on its side, through your account manager or Booking.com's portal. This works as follows: Get Products (`GET /products`) – when Booking.com 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}`) – Booking.com re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Booking.com's side – Booking.com links each Ventrata option and unit to its own listing and ticket types. Your Booking.com account manager does this for you, or you do it in Booking.com's own portal if Booking.com offers one. You don't need to share an API key: Booking.com accesses the connection securely from Ventrata. Typically with Booking.com: Booking.com reads your full product list about every 3 hours. It re-reads each product about every 2 hours. What this means for you: Booking.com can only sell what it has mapped. When you add a product, option or unit in Ventrata, Booking.com may see it on its next refresh, but it won't sell it until it's mapped. So tell your Booking.com account manager whenever you add one.
Content Sync	✅	Booking.com pulls your product content from Ventrata and requires it to meet its content guidelines and minimum requirements. This works as follows: `ventrata/content` capability – Booking.com adds it to the `Octo-Capabilities` header, so Get Products (`GET /products`) and Get Product (`GET /products/{productId}`) also return your product content: titles, descriptions, highlights, inclusions and exclusions, images, FAQs, redemption instructions and location. Booking.com has no interface for suppliers to edit content, so what you set in Ventrata is what Booking.com shows. Booking.com checks content against its guidelines and minimum requirements, and archives or takes offline products that fail, for example with an empty description or an outdated Google Place ID. Typically with Booking.com: Booking.com re-reads your products every few hours, and content changes usually show within about 24 hours. Images are synced by URL, so a replaced image needs a new upload in Ventrata. What this means for you: complete the Minimum Required Content above before Booking.com maps your products, and keep it up to date in Ventrata.
Availability Sync	✅	Booking.com checks your live availability in Ventrata. Ventrata doesn't push availability changes to Booking.com. This works as follows: Availability Check (`POST /availability`) – Booking.com 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 Booking.com needs to book that slot. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Booking.com can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Booking.com: Availability Check: Booking.com checks your products around the clock, usually starting about 6 months ahead and covering 10 days per request, looks up to about a year ahead and re-checks the same product and dates about every 30 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, Booking.com shows it after its next check. For dates it checks regularly, that's within about 30 minutes. Dates further ahead are usually checked less often.
Pricing Sync	✅	Pricing Sync is always on for Booking.com: it pulls your prices from Ventrata with every availability check. This works as follows: `octo/pricing` capability – Booking.com always adds `octo/pricing` to the `Octo-Capabilities` header of its requests, so every availability check includes your prices. 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 Booking.com, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Booking.com 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 Booking.com: Booking.com requests `octo/pricing` on all of its availability checks, so it sells at your Ventrata prices. Booking.com 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 Booking.com. 📗 TIP – Pricing Sync is always enabled for Booking.com, so you don’t need to ask Booking.com to switch it on. Booking.com pulls your prices from Ventrata. 📗 TIP – If prices on Booking.com look wrong, check the Booking.com reseller's pricing in Ventrata first: that's what Booking.com reads.
Promotions Sync	✅	Your Ventrata promotions can apply to Booking.com prices and bookings. This works as follows: `octo/offers` capability – with it, Ventrata applies your eligible promotions to availability prices and to bookings, and Booking.com 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 Booking.com: Booking.com requests `octo/offers`.
Bookings Sync	✅	Bookings, changes and cancellations made on Booking.com 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 Booking.com, Booking.com 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, Booking.com 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. Booking.com gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Booking.com 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 Booking.com, Booking.com 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 Booking.com has to contact you. Change: Booking Update (`PATCH /bookings/{uuid}`) – Booking.com changes existing bookings in place, for example a new date, time or number of people. Typically with Booking.com: Booking.com holds places for about 20 minutes while the customer pays (`expirationMinutes`). A typical Booking.com booking is for about 3 people. It's normal to see more holds than confirmed bookings: holds from customers who don't finish paying simply expire. Booking.com also checks the bookings it has made, with Get Booking (`GET /bookings/{uuid}`) every few minutes, for example to reconcile its records. ‼️ IMPORTANT – Bookings sync one way, from Booking.com to Ventrata. If you cancel, change or rebook a booking from Booking.com in Ventrata, for example in the Dashboard, Booking.com isn't notified. Contact Booking.com so the booking is cancelled or changed on their side too, or ask the customer to cancel through Booking.com.
Pickups/Dropoff Sync	❌	Booking.com doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Booking.com how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Booking.com doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Booking.com how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Booking.com. Customers can only book your main products and options on Booking.com. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Booking.com. Ventrata doesn't notify Booking.com when a ticket is scanned or redeemed. Booking.com only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Booking.com pass holders can't be scanned at your entrance without a booking. Customers from Booking.com need a booking made through Booking.com before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Booking.com. Gift cards bought in Ventrata can't be used on Booking.com, and Booking.com can't sell Ventrata gift cards.

✅ supported · ❌ not supported

Good to know: limits and details of the Booking.com connection

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

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.

My products aren’t live on Booking.com yet.

After you notify your Booking.com contact, mapping usually takes a few business days. Booking.com then checks your content and may run test bookings before the products go live.

Check that the products meet the Minimum Required Content above, especially the Google Place ID.

Booking.com says it can’t find my connection.

Create the Booking.com Attractions connection in your Dashboard first (see Creating the Booking.com Connection). Booking.com accesses it securely from Ventrata, so you don’t need to send an API key or any other details.

My product shows no availability, or Booking.com reports “Provider Inventory Not Found”.

Booking.com currently stores availability up to 180 days ahead, so dates further out don’t show yet. Also check for sales closures and that the product and options are enabled for sale on the Direct API source. If it still looks wrong, ask your Booking.com contact to refresh the product.

Booking.com took my product offline.

The most common causes are a missing or outdated Google Place ID (including on itinerary stops), an empty title, description or inclusions, an FAQ question without an answer, or a flagged word. Fix it in Ventrata, then ask your Booking.com contact to check the product again.

Booking.com rejected my Google Place ID.

Use the Place ID of your exact location on Google, not a service-area business listing, and add it to the supplier or destination address in Ventrata. Changing your Google business profile can make an existing Place ID outdated. Updates usually take about 24 hours to reach Booking.com.

Can I use a different product name, description or other content just for Booking.com?

Not at the moment. Ventrata doesn’t support reseller-specific product content, so Booking.com shows the same name, description and other content as your other channels.

As a workaround, create a separate product with the name and content you want for Booking.com, and build it as a package product that includes your existing product. The package shares the included product’s availability, and you can make it exclusive to Booking.com by allowing it only for the Booking.com reseller. Booking.com then maps it as a new listing, which starts without the reviews of your existing one.

We’re collecting feedback on reseller-specific content for future versions of Ventrata, so tell your Ventrata contact if you need it.

How do I set up a Genius or Deal of the Month promotion?

For Genius and other closed user group deals, create a promotion that is not public, with the code BOOKING_CLOSED_USER_GROUP, allowed only for the Booking.com reseller. For Deal of the Month or a discount for everyone, create a public promotion: it syncs automatically and needs no code. Promotions can’t be combined, so build 10% + 15% as one 25% promotion. See Booking.com Promotions above.

Booking.com shows free cancellation up to the start time.

That’s Ventrata’s default cancellation cutoff of 0 hours. Set the cutoff you want under Product Settings → Cutoffs → Cancellation Cutoff (24, 48 or 72 hours, or non-refundable), and allow about 24 hours for Booking.com to pick it up.

Booking.com shows my start times as time ranges.

Booking.com currently shows a start and end time for every OCTO product, even when it has fixed start times. Booking.com is looking at showing only the start time for these products. You don’t need to change anything in Ventrata.

I have several Ventrata accounts, for example one per country.

Create a Booking.com Attractions connection in each account, then tell your Booking.com contact which accounts belong together so they can group them under one supplier.

📚 More about Ventrata connections

Partner Information

Booking.com B.V.

Oosterdokskade 163

1011 DL Amsterdam, Netherlands

Postal address:

Postbus 1639

1000 BP, Netherlands

booking.com/attractions

Ventrata Partner ID: f1a00451-151a-4376-9d76-ee06d57981c3

Booking.com: Reseller Connection

Creating the Booking.com Connection

Mapping Products to Booking.com

Minimum Required Content

Booking.com Promotions

Managing the Booking.com Connection

Connection Features Detailed

FAQs

Partner Information