Skip to main content

isango!: Reseller Connection

Connect isango! to Ventrata to sync availability and prices and receive bookings instantly. Specialist in hop-on hop-off and skip-the-line.

isango! logo

 

isango! is a specialist retailer of tours, experiences and attraction tickets within HBX Group, listing more than 10,000 products across 800-plus destinations sourced from local operators worldwide, sold in English, German and Spanish and 11 currencies. For operators, it brings city sightseeing buyers, hop-on hop-off, skip-the-line and attraction-pass shoppers, reached through its own site, themed sites such as Hop-On Hop-Off Bus, Attraction Passes and The Boat Tours, and white-label deals with airlines and travel companies.

 

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

 

To learn more about partnering with isango!, visit isango.com.

 

Primary website

Tags

OTA · Tours & Activities OTA

Destination markets

🌎 Global

Source markets

🌎 Global

Specialties

Hop-on hop-off, skip-the-line and city sightseeing

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

isango! (using Ventrata's OCTO API)

 

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

  • Availability Sync – isango! checks your live availability in Ventrata.

  • Pricing Sync – isango! gets your prices from your reseller pricing in Ventrata.

  • Bookings Sync – bookings, updates and cancellations from isango! are created in Ventrata instantly, and customers get Ventrata tickets.

 

Creating the isango! Connection

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

Before you begin:

  • You must have a commercial agreement with isango! for them to sell your products. To inquire about partnering with them, contact them via isango.com.

  • You must have isango! 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.

 

  1. In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select isango! from the list of partners.

  2. Select isango! 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.

  3. (Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple isango! connections and would like to differentiate between them more easily in the future.

  4. 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 isango!

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

 

 

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

 

📗 TIP

isango! 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 isango! Connection

  • Allow or disallow products: limit which destinations, products and options isango! can access. See how to allow or disallow products.

  • Rename the connection to tell several isango! connections apart.

 

Connection Features Detailed

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

 

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

 

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

 

Product Mapping

❌

You can't map products from Ventrata. isango! maps them on its side, through your account manager or isango!'s portal.

This works as follows:

  • Get Products (GET /products) – when isango! 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}) – isango! re-reads a single product to pick up changes to its options, units, booking cutoffs and settings.

  • Mapping on isango!'s side – isango! links each Ventrata option and unit to its own listing and ticket types. Your isango! account manager does this for you, or you do it in isango!'s own portal if isango! offers one. You only share the connection's API key.

 

Typically with isango!:

  • isango! reads your full product list about every 9 hours.

  • It re-reads each product about every 10 hours.

 

What this means for you: isango! can only sell what it has mapped. When you add a product, option or unit in Ventrata, isango! may see it on its next refresh, but it won't sell it until it's mapped. So tell your isango! account manager whenever you add one.

Content Sync

✅ / ❌

isango! can read your product content, such as descriptions and images, from Ventrata.

This works as follows:

  • octo/content capability – when isango! 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 isango! on its next product refresh.

 

Typically with isango!:

  • isango! requests octo/content.

Availability Sync

✅

isango! checks your live availability in Ventrata. Ventrata doesn't push availability changes to isango!.

This works as follows:

  • Availability Check (POST /availability) – isango! 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 isango! needs to book that slot.

  • Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so isango! can't overbook a slot that has just sold out, even if its stored availability is slightly out of date.

 

Typically with isango!:

  • Availability Check: isango! checks your products throughout the day, usually starting today and covering 3 days per request, looks up to about 8 months ahead and re-checks the same product and dates about every 12 hours.

  • Checks are busiest between 00:00 and 06:00 UTC, which suggests most checks are live, as customers browse isango!.

 

What this means for you: when you close a date, change capacity or sell out in Ventrata, isango! 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 isango! asks for them with the octo/pricing capability.

This works as follows:

  • octo/pricing capability – isango! 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 isango!, both from the reseller's pricing in Ventrata (retail and wholesale/commission).

  • Group prices – when isango! 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 isango!:

  • isango! requests octo/pricing on all of its availability checks, so it sells at your Ventrata prices.

  • isango! sends the number of people per unit type, so group prices are calculated for the actual booking.

 

‼️ IMPORTANT – Ask for pricing to be enabled. When you ask isango! to map your products, ask them to enable pricing (octo/pricing) as well, or switch it on yourself if you map in isango!'s portal. Otherwise it may be off, and isango! won't receive your Ventrata prices.

📗 TIP – If prices on isango! look wrong, check the isango! reseller's pricing in Ventrata first: that's what isango! reads.

Promotions Sync

❌

Your Ventrata promotions don't apply on isango!.

Prices on isango! don't include promotions you create in Ventrata. Set up any promotions with isango! directly.

Bookings Sync

✅

Bookings and cancellations made on isango! are created in Ventrata instantly, and customers get Ventrata tickets.

This works as follows:

  1. Hold: Booking Reservation (POST /bookings) – when a customer starts checkout on isango!, isango! 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.

  2. Confirm: Booking Confirmation (POST /bookings/{uuid}/confirm) – once payment goes through, isango! 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. isango! gives these to the customer, who shows them at your entrance like any Ventrata ticket.

  3. Expire: if the customer doesn't finish paying, isango! never confirms, and the hold expires on its own and frees the places.

  4. Cancel: Booking Cancellation (POST /bookings/{uuid}/cancel) – when a customer cancels on isango!, isango! 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 isango! has to contact you.

  5. Change: isango! doesn't use Booking Update (PATCH /bookings/{uuid}), so a change most likely reaches Ventrata as a cancellation plus a new booking.

 

Typically with isango!:

  • isango! doesn't set a hold time, so the default hold time applies.

  • A typical isango! booking is for about 2 people.

 

‼️ IMPORTANT – Bookings sync one way, from isango! to Ventrata. If you cancel, change or rebook a booking from isango! in Ventrata, for example in the Dashboard, isango! isn't notified. Contact isango! so the booking is cancelled or changed on their side too, or ask the customer to cancel through isango!.

Pickups/Dropoff Sync

✅ / ❌

isango! sends pickup details with its bookings.

This works as follows:

  • octo/pickups capability – isango! 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 isango!:

  • isango! sends pickup details with its bookings.

Custom Questions Sync

✅ / ❌

isango! sends answers to your booking questions with its bookings.

This works as follows:

  • octo/questions capability – isango! reads the questions set on your products and sends the customer's answers with the booking, where you see them in Ventrata.

 

Typically with isango!:

  • isango! sends answers to your booking questions.

Extras Sync

❌

Extras and add-ons can't be booked through isango!.

Customers can only book your main products and options on isango!. Sell extras separately, for example on arrival.

Redemption Sync

❌

Redemptions aren't reported to isango!.

Ventrata doesn't notify isango! when a ticket is scanned or redeemed. isango! only sees a redemption if it reads the booking back from Ventrata.

Pass Walkup Scanning Sync

❌

isango! pass holders can't be scanned at your entrance without a booking.

Customers from isango! need a booking made through isango! before they visit.

Gift Card Sync

❌

Ventrata gift cards can't be sold or redeemed through isango!.

Gift cards bought in Ventrata can't be used on isango!, and isango! can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

 

Good to know: limits and details of the isango! connection

  • Delays: availability and prices reach isango! only when it checks, so there's always a short delay after you change something in Ventrata.

  • Cancellation cutoff: isango! can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.

  • What isango! 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: isango! issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.

  • Test bookings: isango! 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 isango!.

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.

 

 

Partner Information

Isango Travel Limited

4th Floor, 399-401 Strand

London, WC2R 0LT, United Kingdom

 

Ventrata Partner ID: 130f5b49-3a2d-4650-9f1d-c1c889186f35

Did this answer your question?