OneConnect is our one-stop solution for supplier integration. You can now have easy access to inventory and availability information from multiple suppliers with just a single integration.

Our expertise in supplier aggregation enables our customers to focus more on their business and less on technology. Our easy-to-integrate and ready-to-use APIs help you build an end-to-end hotel booking solution with minimal time, cost, and complexity.

OneConnect enables you be ahead of the competitive travel business industry by providing the following powerful capabilities:

  • Supplier Aggregation: Aggregate inventory from multiple suppliers. Get worldwide coverage and supplier integration in a fraction of time and effort.
  • Deduplication: Group the same hotels that come from various suppliers, which, in turn, allows you to select the cheapest hotel from multiple suppliers or choose hotels from suppliers that provide the highest yield.
  • Streaming APIs: Our asynchronous APIs allow you to consume results as soon as they are returned by suppliers.
  • Multi-room Booking: Seamlessly search for multiple rooms and book multiple rooms together.
  • Cloud-first Architecture: High availability and scalability. You no longer need to worry or compromise on downtime.
  • Plug-and-play Architecture: Flexibility to write your own connectors and plug your own supplier integrations.

OneConnect Architectural Workflow

The following diagram depicts the OneConnect architecture. As illustrated, you no longer need to worry about creating various connectors to obtain worldwide coverage and aggregate inventory from multiple suppliers. OneConnect seamlessly takes care of this for you with just a single integration. All you need to do is to integrate your travel solution or engine with OneConnect and it seamlessly uses its wide variety of supplier connectors to obtain hotel inventory and availability information. Additionally, OneConnect also comes with a flexible plug-and-play architecture. You can easily write your own connectors (custom connector) to plug your own supplier integrations.

image1

Figure 1: OneConnect Architectural Diagram

OneConnect API Workflow

We have designed the OneConnect API workflow keeping in mind two different business use cases as the entry points in the workflow, one that enables search by location (hotel listing) and the other that enables search by hotel ID (room listing), which comes in handy for hotel ads or promotions. The OneConnect API workflow consists of three to four main steps (verbs) depending on your use case's entry point, which starts with the hotel search by location (hotel listing) or search by hotel ID (room listing) call, and then moves ahead with the call to get the room rates, followed by a call to get the rate rules, and then final step, which is a call to book one or more rooms in a single booking. We also provide the Cancel API, which is an optional step in the workflow.

The following diagram describes the OneConnect API workflow:

image1

Figure 2: OneConnect API Workflow

Note: For a seamless experience, we have provided two use cases for you to try out, namely a per-booking pricing model use case and a per-room pricing model use case. You must verify the pricing model that is returned in the response of the Get Room Rates Results API, and then use the appropriate pricing model call in the Get Rate Rules and Book APIs. For example, if the response from the Get Room Rates Results API call returns a per booking pricing model from the supplier, you must use the Get Rate Rules - Per Booking use case, the Book - Per Booking use case, and then the Cancel - Per Booking use case.

The following procedure describes each step in the OneConnect API workflow:

  1. Before you begin to use OneConnect APIs, you must decide the appropriate entry point based on your business use case.
    • If you want to search for hotels around a specific location or point of interest, your entry point will be the Hotel Search API. Proceed to [step 2](#step2).
    • If you want to directly search for rooms, along with the room rates and policies, in a specific hotel (search by hotel ID), you must skip step 2 and directly proceed to [step 3](#step3).
  2. Search for hotels by using the Hotel Search APIs. The Hotel Search API workflow involves the following three-step process:
    a. Call the Initiate Hotel Search API. You can search for hotels based on a hotel ID or a geolocation, which includes a radial search, a rectangular search, or a polygonal search.
    b. Call the Get Hotel Search Results API to get the search results.
    c. Optional: Call the Get Static Content APIs to get the hotel's static content attributes, such as the hotel's amenities, policies, or images. The hotel content attributes are obtained from clarifi.
  3. Retrieve a list of rooms for a specific hotel, along with their rates and content attributes, by using the Get Room Rates APIs. The Get Room Rates API workflow involves the following three-step process:
    a. Call the Initiate Get Room Rates API. Note that there are two use cases for the Get Room Rates API:
    • If you reached this step by performing a prior hotel search, you must initiate a Stateful Room Rates API call.
    • If you are entering the workflow by searching directly for rooms in a specific hotel, you must initiate a Standalone Room Rates API call.
    b. Call the Get Room Rates Results API.
    c. Optional: Call the Get Static Content APIs to get the hotel's static content attributes, such as the hotel's amenities, policies, or images. The hotel content attributes are obtained from clarifi.
  4. Retrieve the latest room rates with all the rules, policies, and restrictions around the usage of that specific room rate, by using the Get Rate Rules API. At this step, you can also optionally call the Get Static Content APIs to get the hotel's static content attributes, such as the hotel's amenities, policies, or images.
  5. Book one or more rooms in a hotel by using the Book API.
  6. If required, cancel a confirmed booking by using the Cancel API.

HTTP Headers

The following table lists the request headers that you must provide, in standard HTTP 1.1 format, when you call our REST APIs. Our REST APIs return the standard HTTPS response headers. To view example headers, see the headers section of the API sample code in the documentation. You can also read more about header field definitions here.

HTTP Request Header FieldDescriptionSample Value
oski-tenantId
Required
Tenant ID. This is used to identify the tenant that is making the request. If you do not know your tenant ID, please contact OneConnect Business Team.Demo
oski-user-ip
Required
IP address of the customer. The customer is the end-user who is making the booking. Ensure that your integration passes the customer's IP address instead of your own IP address. This is required for suppliers who have IP-restricted access to their inventory.

The customer's IP address helps determine their location and assign the correct payment gateway. The IP address can also be used for fraud recovery and other analytics.
127.0.0.1
Content-Type
Required
MIME type of the body of the request. This is used to identify the type of request.application/json
Accept-Language
Optional
Language in which you want to retrieve the hotel content attributes. For example, when you set the value in the `accept-language` to `es-ES` (Spanish (Spain)), then the hotel content attributes such as the hotel description, hotel rating, contact information, images, amenities, and policies are returned in Spanish (Spain) from the supplier.

If the hotel content attributes are not available with the supplier in the language set in the `accept-language` header, the API returns the hotel content attributes in the default language set for the supplier.
en-US
Accept-Encoding
Optional
List of acceptable encodings. This restricts the content-codings that are acceptable in the response. See HTTP compression.gzip

Endpoints and URLs

The following tables list the endpoints for the Hotel APIs.

Hotel Search

APIMethodBase URLEndpoint
Initiate Hotel SearchPOSThttps://usg.cnxloyalty.com/api/hotels/search/init
Get Hotel Search ResultsGET/api/hotels/search/{sessionId}/results

Room Rates

APIMethodBase URLEndpoint
Initiate Room Rates SearchPOSThttps://usg.cnxloyalty.com/api/hotels/getroomrates/{sessionId}/init
/api/hotels/getroomrates/init
(stand-alone room rates search)
Get Room Rates ResultsGET/api/hotels/getroomrates/{sessionId}/{hotelId}/results

Get Rate Rules

APIMethodBase URLEndpoint
Get Rate RulesPOSThttps://usg.cnxloyalty.com/api/hotels/getraterules/{sessionId}

Book

APIMethodBase URLEndpoint
BookPOSThttps://usg.secure.cnxloyalty.com/api/hotels/book/{sessionId}

Cancel

APIMethodBase URLEndpoint
CancelPOSThttps://usg.cnxloyalty.com/api/hotels/cancel



Go to the Search API >>

For any query or suggestions, feel free to drop an email to support@one-connect.io