RhomTrip is a New York-based ground transportation specialist founded in 2018, supplying airport transfers, chauffeur service and group, corporate and MICE transport worldwide through licensed local suppliers. For operators, it brings trade demand only: independent travel advisors, host agencies, tour operators, travel management companies and online travel agencies booking transfers and transport for their clients, with Fora Reserve advisors among them, so bookings are long-lead and often group or corporate.

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

To learn more about partnering with RhomTrip, visit rhomtrip.com.

Primary website	rhomtrip.com
Tags	B2B Marketplace
Destination markets	🌎 Global
Source markets	🌎 Global
Specialties	Transfers and group transport booked by travel advisors
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Developed by	RhomTrip (using Ventrata's OCTO API)

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

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

Creating the RhomTrip Connection

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

Before you begin:

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

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

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

📗 TIP

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

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

Connection Features Detailed

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

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

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

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

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the RhomTrip connection

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

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

RHOMTRIP OU

Linda tn 2, Narva linn, Ida-Viru maakond, 20309

Estonia

rhomtrip.com

Ventrata Partner ID: 6e14f64d-0ef2-490c-b499-509db5c67c0c

RhomTrip: Reseller Connection