CityWalkers is an Italian walking tour operator and reseller running tip-based free walking tours plus scheduled group and private departures in Milan, Florence, Rome, Venice, Verona, Naples, Pompeii and Assisi, with London outside Italy. For operators, it brings travelers already walking a city with its guides, converting free-tour participants into paid bookings for museum entries such as the Uffizi, Accademia and Vatican, cooking classes, wine tastings and archaeologist-led site visits.

Connecting CityWalkers to Ventrata will sync your availability and prices and deliver bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with CityWalkers, visit www.citywalkers.eu.

Primary website	www.citywalkers.eu
Tags	Operator Reselling Others
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Free walking tour guests upgrading to paid museum entries
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$100k+
Developed by	CityWalkers (using Ventrata's OCTO API)

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

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

Creating the CityWalkers Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ❌ not supported

Good to know: limits and details of the CityWalkers connection

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

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

CityWalkers Ltd

7 Bell Yard

London, England, WC2A 2JR, United Kingdom

citywalkers.eu

Ventrata Partner ID: 89199f1c-188a-4b3a-afc7-1ea2972b6346

CityWalkers: Reseller Connection