WeKnow is a London travel aggregator for inbound visitors, bundling attraction entry, walking and private car tours, theater seats, airport transfers, rail and coach tickets and UK SIM cards in one storefront. For operators, it brings international arrivals who book transfers and headline attractions together around their arrival, paying in pounds, dollars or euros, with hop-on hop-off, museum and studio tours among the products sold alongside.

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

To learn more about partnering with WeKnow, visit weknowlondon.com.

Primary website	weknowlondon.com
Tags	OTA · Tours & Activities OTA
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Arrival bundles of transfers and headline attractions
Connection features	Availability Sync · Pricing Sync · Bookings Sync · Pickups/Dropoff Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Developed by	WeKnow (using Ventrata's OCTO API)

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

Availability Sync – WeKnow checks your live availability in Ventrata.
Pricing Sync – WeKnow gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from WeKnow are created in Ventrata instantly, and customers get Ventrata tickets.
Pickups/Dropoff Sync – WeKnow sends pickup and drop-off details with its bookings to Ventrata.

Creating the WeKnow Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the WeKnow connection

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

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

WE KNOW GROUP LIMITED

Ru0019 Arrival Concourse, Terminal 5 London Heathrow Airport

Hounslow, England, TW6 2GA, United Kingdom

weknowlondon.com

Ventrata Partner ID: dcc24eda-3ea3-4801-b348-d34852f9ec14

WeKnow: Reseller Connection