Rathin Tourism is a Dubai travel and ticketing agency based in Meena Bazar, Bur Dubai, selling desert safaris, city tours and theme park admissions across the UAE to walk-in and online travelers and agent partners. For operators, it brings visitors already on the ground in Dubai buying safaris, tours and park admission for the coming days, plus its agent partners, a small local reseller close to the point of decision.

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

To learn more about partnering with Rathin Tourism, visit rathin.com.

Primary website	rathin.com
Tags	Operator Reselling Others
Destination markets	🇦🇪 UAE
Source markets	🌎 Global
Specialties	Walk-in sales of desert safaris, city tours and theme parks
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Rathin Tourism (using Ventrata's OCTO API)

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

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

Creating the Rathin Tourism Connection

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

Before you begin:

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

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

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

📗 TIP

Rathin Tourism 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 Rathin Tourism Connection

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

Connection Features Detailed

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

In short: Rathin Tourism pulls everything it needs from Ventrata. It reads your products, checks your availability (and your prices, when it asks for them), and sends bookings and cancellations. Ventrata doesn't push changes to Rathin Tourism, so anything you change in Ventrata reaches Rathin Tourism the next time it checks.

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Rathin Tourism connection

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

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

Rathin Tourism LLC

rathin.com

Ventrata Partner ID: 1868d9ad-da8a-48ba-be6a-699c1331177c

Rathin Tourism: Reseller Connection