¶ Welcome
¶ About the Juniper WebService
The Juniper WebService is an API designed to facilitate seamless integration between third-party systems and the Juniper Booking Engine. This guide aims to enhance your understanding of the Juniper WebService and support your development process for third-party applications. WebServices are used to automate administrative tasks traditionally performed manually, resulting in the following benefits:
- Elimination of workflow bottlenecks
- Reduction of human errors
However, it's essential to note the following challenges:
- Lack of human assessment in certain tasks
- Does not replace essential marketing or product communication efforts
The Juniper WebService communicates using XML, a structured text format for transmitting information. While XML ensures consistent data exchange, it does not inherently resolve issues if errors occur.
¶ Assumptions
This guide assumes you are already familiar with:
- XML schemas and specifications
By utilizing the Juniper WebService, clients—such as web applications, mobile devices, and more—can connect directly to the reservation system, enabling efficient and automated booking operations.
¶ Getting Started
To begin integrating with the Juniper API, your first step is to contact the Juniper supplier you have agreed to connect with and provide them with the following details:
- Company name and primary technical contact information (name, title, phone, and email)
- The services or products you would like to access (e.g., hotels, transfers, services, etc.)
Once you've shared your contact details with the Juniper Seller, you will need to sign up and your account needs to be verified on the Juniper Buyer Portal (https://buyers-portal.junipertraveltech.com/), once done, you will be able to manage and whitelist the IP addresses for your development environment connection.
After you provide the required information to the Juniper supplier, our team will contact yours using the email address you submitted. At this point, we will confirm that your IP addresses have been successfully whitelisted and may request any additional details if necessary.
After receiving this information, the Juniper API support team will:
- Set up test environment credentials and provide them to you for your integration development
- Share the endpoint required to connect to the Juniper API deveopment environment
For reference, here is the development environment relevant endpoints:
https://xml-uat.bookingengine.es/WebService/JP/WebServiceJP.asmx
And, whose WSDL you would also be able to find under:
https://xml-uat.bookingengine.es/WebService/JP/WebServiceJP.asmx?WSDL
Important note:
The domain xml-uat.bookingengine.es corresponds to the development and test environment. If you wish to connect to a different environment (e.g., the live environment or multiple Juniper Sellers), you will need to replace this domain accordingly. Ensuring the correct endpoint is used is critical to successful integration.
¶ Generic Integration Process
In order to understand the JP WebService work flow, we've prepared a flow chart that outlines and simplifies all of the steps that need to be taken through the booking process. We will refer to this flow chart as we advance further on our explanation.
To know more keep on reading! Go directly to the API you need for your integration process or the proceed to the Generic Workflow to walk you trough our workflow
¶ API Reference
Here you will find all the specifications you will need to integrate all the Juniper API services
¶ Products API
These API collections will provide you the necessary tools to integrate with the Juniper Booking Engine
- JP Common API
- JP Hotel API
- JP Hotel Inventory API
- JP Hotel PUSH API
- JP Car API
- JP Package API
- JP Flight API
- JP Cruise API
- JP Insurance API
- JP Transfer API
- JP Ticket API
- JP Visa API
- JP Payment Process API
¶ Management API
These API collections will provide you the necessary tools to export information from the Juniper Booking Engine to an external system such as ERP solutions or an external Booking Engine
¶ Channel Manager API
These API collections will provide you the necessary tools to to integrate as a Channel Manager or Push integration on the Juniper Booking Engine
¶ OTA Standard API
The OpenTravel Alliance provides a community where companies in the electronic distribution supply chain work together to create an accepted structure for electronic messages, enabling suppliers and distributors to speak the same interoperability language, trading partner to trading partner, these collection of APIs are the implementation for these standards developed by Juniper. As per the standard rules these APIs are restricted to these standards offer lower level of customization as oposed to the Juniper JP implementation, thus Juniper only offers a limited support and a limited subset of the functionality that the OTA offers
¶ Deprecated API
These APIs collections are kept as a reference and considered deprecated. If your integration uses an API of this collection, we strongly recommend to implement the newer updated and mantained version