Vox City is the consumer arm of Vox Group, selling guided and self-guided walking tours that pair live guides with a multilingual audio-guide app travelers follow at their own pace, in cities across Europe, the Middle East, Asia and North America. For operators, it brings independent city-break visitors in Rome, London, Paris, Amsterdam, Dubai and Bangkok, booking in five website languages and bundling attraction entry with audio commentary across more than 200 sites.

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

To learn more about partnering with Vox City, visit voxcity.com.

Primary website	voxcity.com
Tags	Operator Reselling Others · Audio Guides & Self-Guided
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Guided and audio-guided walks bundled with attraction entry
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Vox City (using Ventrata's OCTO API)

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

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

Creating the Vox City Connection

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

Before you begin:

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

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

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

📗 TIP

Vox City 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 Vox City Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Vox City connection

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

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

VOX CITY INTERNATIONAL LIMITED

277-279 Chiswick High Road, Chiswick, London, W4 4PU

United Kingdom

voxcity.com

Ventrata Partner ID: 80a5920d-3ab1-4b38-a96e-c3945519c160

Vox City: Reseller Connection