Visit London is the official visitor guide to London, published by London & Partners, the capital's growth agency backed by the Mayor of London, selling West End theater seats, attraction entry, sightseeing tours, hotel stays and the London Pass. For operators, it brings around 22 million people a year planning a London trip, domestic and international visitors who book attractions and theater alongside their stay.

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

To learn more about partnering with Visit London, visit visitlondon.com.

Primary website	visitlondon.com
Tags	Destination Organization (DMO)
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Official London trip planning with theater and attractions
Connection features	Availability Sync · Bookings Sync
Developed by	Visit London (using Ventrata's OCTO API)

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

Availability Sync – Visit London checks your live availability in Ventrata.
Bookings Sync – bookings, updates and cancellations from Visit London are created in Ventrata instantly, and customers get Ventrata tickets.

Creating the Visit London Connection

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

Before you begin:

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

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

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

📗 TIP

Visit London 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 Visit London Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Visit London connection

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

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

London & Partners Limited

169 Union Street, London, SE1 0LL

United Kingdom

visitlondon.com

Ventrata Partner ID: 9caedfd6-2895-48ac-b848-2bda5c73c318

Visit London: Reseller Connection