Lovetovisit is a UK discovery and booking platform for days out, covering theaters, zoos, theme parks, aquariums, museums, sport, live events and family attractions at discounted rates with no membership fee, operated by The Social Commerce Platform Ltd with partner portals and white-label storefronts. For operators, it brings UK domestic families and day-trippers planning something to do near home, with demand weighted toward destinations outside London and deal-led buyers who respond to discounted tickets.

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

To learn more about partnering with Lovetovisit, visit lovetovisit.com.

Primary website	lovetovisit.com
Tags	OTA · Tours & Activities OTA
Destination markets	🇬🇧 UK
Source markets	🇬🇧 UK
Specialties	Discounted family days out near home
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	Lovetovisit (using Ventrata's OCTO API)

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

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

Creating the Lovetovisit Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Lovetovisit connection

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

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

THE SOCIAL COMMERCE PLATFORM LTD

5th Floor East, Churchill House, 17 Churchill Way

Cardiff, Wales CF10 2HD, United Kingdom

lovetovisit.com

Ventrata Partner ID: 199641d6-021f-43a1-bef0-3880e25635d9

Lovetovisit: Reseller Connection