Ashana Travels is a London-based travel agency selling hop-on hop-off bus tours, flexible sightseeing passes and attraction tickets for landmarks including the London Eye and the Tower of London. For operators, it brings visitors to London buying sightseeing and admissions through an agency storefront.

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

To learn more about partnering with Ashana Travels, visit ashanatravels.com.

Primary website	ashanatravels.com
Tags	Travel Agent · Sightseeing & Hop-On Hop-Off
Destination markets	🇬🇧 UK
Source markets	🌎 Global
Specialties	London sightseeing and landmark tickets
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	Ashana Travels (using Ventrata's OCTO API)

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

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

Creating the Ashana Travels Connection

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

Before you begin:

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

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

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

📗 TIP

Ashana Travels 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 Ashana Travels Connection

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Ashana Travels connection

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

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

Ashana Travels

ashanatravels.com

Ventrata Partner ID: 019f8f53-a40e-7e8b-9a21-bb912af7d021

Ashana Travels: Reseller Connection