Juniper integration
When a wholesaler or DMC tells you “we work on Juniper, we will send your XML user”, the technical side is already finished on ours. We enter the access they give you and their hotels appear in Travelrobot.
Who is Juniper?
Juniper is not a supplier, and nobody buys a room from Juniper. It is the booking engine behind a great many companies that do sell rooms. That is why the name keeps coming up when you talk connectivity with a new partner.
Juniper Travel Technology has been at this since 2003. By the company’s own description, its Booking Engine is used by wholesale tour operators, incoming agencies, online travel agencies and bed banks, and XML web services are one of the distribution channels it gives them. A supplier on Juniper loads its hotel contracts into the engine and then hands XML users to the agencies it wants to sell to. You are at the other end of that XML.
How KPLUS connects to Juniper
We wrote the client for Juniper’s XML service in Travelrobot. Because every Juniper customer exposes the same interface, the work is done once. After that, each supplier is simply a new set of credentials entered in Travelrobot. The DMC you use for one destination and the wholesaler you use for another both arrive through the same connector, each with its own contract and its own prices.
The agreement is between you and that supplier. Juniper is its software vendor and KPLUS is yours.
What you can do with the Juniper integration
For every Juniper supplier, hotels are searched in the shared result list, a hotel opens with its room and board options and their prices, and the cancellation policy is read for the option you pick.
Juniper keeps checking and booking apart. After you choose a room, the price is validated with the supplier, and the pre-book step confirms price and availability once more before any record is created. With DMC contracts this matters a great deal. Between your search in the morning and the customer’s decision in the afternoon, a stop sale may have closed the hotel. You get the refusal at pre-book and not in an email the next day.
Confirmed bookings are cancelled or voided from Travelrobot, and the request goes to the supplier’s Juniper system. The integration covers accommodation today. Flights, transfers or packages the same supplier may sell on Juniper are not integrated yet, and we can add them for an agency that needs them.
Who it is for
For agencies that buy from several destination suppliers the gain is plain. Each new partner on Juniper becomes a matter of entering credentials.
Wholesalers and tour operators that resell third-party hotel stock to their own sub-agents widen their range without logging in to five different extranets.
Frequently asked questions
My supplier uses Juniper. What do you need from me?
The XML access the supplier has issued to you. With it we set the supplier up in Travelrobot, and you run a trial search before you start selling.
Can I connect more than one supplier that runs on Juniper?
Yes. Each one is set up separately with its own credentials, and the prices come from your contract with that supplier.
Do I need a contract with Juniper?
No. Juniper is the supplier’s technology vendor. Your contract is with the supplier.
Do the supplier’s transfers or flights come through as well?
Not today. The connection covers hotel search and booking. If you need another product your supplier sells through Juniper, it can be integrated.
