Sightseeingo is a UK-registered online travel agency (OTA) for sightseeing covering more than 250 destinations worldwide, with hop-on hop-off bus tours as the flagship category alongside walking tours, museum tickets, combo tickets and attraction passes. For operators, it brings international city-break travelers buying sightseeing tours and attraction entry, strongest in Europe and the UAE, from a curated base of about 100 suppliers and roughly 159,000 completed orders.

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

To learn more about partnering with Sightseeingo, visit sightseeingo.com.

Primary website	sightseeingo.com
Tags	OTA · Tours & Activities OTA · Sightseeing & Hop-On Hop-Off
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Hop-on hop-off bus tours and city sightseeing
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Ventrata Booked Suppliers (last 12 months)	10+
Developed by	Sightseeingo (using Ventrata's OCTO API)

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

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

Creating the Sightseeingo Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Sightseeingo connection

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

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

Sightseeingo Ltd

C/O Bnw Accountants Ltd, Unit 9105 Access House, 141 Morden Road

Mitcham, England CR4 4DG, United Kingdom

sightseeingo.com

Ventrata Partner ID: 28bf6362-8c67-4592-abed-a2af5d29ae11

Sightseeingo: Reseller Connection