Frequently Asked Questions

Check out some general and technical frequently asked questions and answers about Cleartrip API.

Hotels API Reference

Contents

Introduction

The Cleartrip hotel API allows a user to search and book hotel rooms using a REST based service. XML is used for server/client communication. The user needs a key (known as the API Key), to use this API. You can read more about REST, XML and the API key in the Getting Started Guide.

Service URLs: The service is available at api.cleartrip.com. Access to the staging (test) environment is available at api.staging.cleartrip.com.

Schema files have been provided in XML Schema Definition (XSD) format. Schema files have been defined wherever XML is required (either as request or response).

This document is intended for Developers and business analysts working with affiliates/partners tasked with integration to the Cleartrip.com website.

A conceptual understanding of Internet and search technologies as well as strong familiarity with XML and HTTP protocol is necessary.


Using the API Key

The API key is generated when the user’s API account is activated. The API key should be sent as the value of the X-CT-API-KEY HTTP header with every API request. Along with API key should be sent as the value of the X-CT-SOURCETYPE=API HTTP header with every API request. Failure to send an API key will mean result in an HTTP 403 (Forbidden) response. Also, X-CT-SOURCETYPE = 'API' should be sent in the header for every API request. For Whitelabel Integration, X-CT-SOURCETYPE = 'B2C' should be sent in the header.


Suggested transaction flow

We suggest the following process/transaction flow in integrating with the Cleartrip APIs.

Hotel API Transaction Flow

Provides the Cleartrip hotel search. The search request is a simple HTTP GET request. The query parameters described below should be sent alongwith with the search URL, and the user’s API key in the HTTP headers. A successful response will always return the HTTP status code 200. (Note that a status code of 200 doesn’t necessarily mean that you the search result will be returned; but a successful search will always return a status code of 200).

Request details

Production URL:
https://api.cleartrip.com/hotels/1.0/search
Staging URL:
http://api.staging.cleartrip.com/hotels/1.0/search
Method:
GET
Sample Request for search criteria 2 Rooms, 3 Adults, 1 Child, 2 Nights:
http://api.staging.cleartrip.com/hotels/1.0/search?check-in=2014-04-01&check-out=2014-04-03&no-of-rooms=2&adults-per-room=2,1&children-per-room=1,0&city=Mumbai&state=Maharashtra&country=IN
Sample Request for search criteria 1 Rooms, 2 Adults, 0 Children, 2 Nights:
http://api.staging.cleartrip.com/hotels/1.0/search?check-in=2014-05-02&check-out=2014-05-04&no-of-rooms=1&adults-per-room=2&children-per-room=0&city=Bangalore&state=Karnataka&country=IN
Sample Request for search by Hotel Id:
http://api.staging.cleartrip.com/hotels/1.0/search?check-in=2014-04-01&check-out=2014-04-03&no-of-rooms=3&adults-per-room=1,1,1&children-per-room=1,0,1&city=Bangalore&state=Karnataka&country=IN&ct_hotelid=423327
Sample Request for search with age of children : 2 Rooms, 1st room - 1 adult, 2 children(age 4 and 6 yrs), 2nd room - 1 adult, 1 child(age 9 yrs), 2 Nights:
http://api.staging.cleartrip.com/hotels/1.0/search?check-in=2014-04-01&check-out=2014-04-03&no-of-rooms=2&adults-per-room=1,1&children-per-room=2,1&ca1=4&ca1=6&ca2=9&city=Bangalore&state=Karnataka&country=IN

Search parameters

The various search parameters are described below:

Name Description Format Example
check-in Check-in date Valid ISO Date Format (YYYY-MM-DD) 2014-04-01
check-out Check-out date Valid ISO Date Format (YYYY-MM-DD) 2014-04-04
no-of-rooms Number of rooms Valid integer not greater than 4 2
adults-per-room Number of adults per room Comma seperated list of valid integers. Number of items in the list should be equal to the number of rooms requested. If the number of requested rooms is 2 and if one adult is going to stay in each room, then pass 1,1
children-per-room Number of children per room Comma seperated list of valid integers. Number of items in the list should be equal to the number of rooms requested. If the number of requested rooms is 2 and one child is going to stay in one of the rooms, with the other room not containing any children, then pass 1,0
ca# This is a parameter which states the age of the children. This parameter is optional but recommended. If this parameter is not passed, child's age is taken as 11 by default. Valid age. Number of items in the list should be equal to the number of children staying. If the number of requested rooms is 2 and two children of age 4 and 6 are going to stay in the 1st room and one child of age 9 is going to stay in the 2nd room, then pass ca1=4&ca1=6&ca2=9
city City name to search for hotels Valid city name Mumbai
country Two letter ISO country code Should be valid ISO country code IN
hotel-info This is an optional parameter which determines if hotel content information (either full or partial) is required as part of the search response or not.
no:
no info will be returned
detail:
detail info will be returned
null or invalid value:
only basic info will be returned
no / detail

Restrictions on the search parameters

These are the restrictions on the search parameters.

  • Check-out date should be greater than the check-in date.
  • Either of the dates should not beyon a year of the search date.
  • The number of rooms requested has to be between 1 and 4.

Response details

If the search was successful, the response body returns an XML alongwith the HTTP status code 200. If any error is encountered during search, the response body will contain an XML with the root element error. See the schema and sample search result XML for more details.

Response content type:
application/xml
Response schema details:
search-response.xsd
Sample response XML:
Sample Response for search criteria 2 Rooms, 3 Adults, 1 Children, 2 Nights
Sample Response for search criteria 1 Room, 2 Adults, 0 Children, 2 Nights
Sample Response for search by Hotel Id
Search Response Description:

Name of the tag

 Descriptions

search-criteria

The parameters with which the search request is made

currency

The currency in which the prices of hotels are displayed.

base-url

The URL which is to be considered as base for all subsequent requests 

hotels

Contains the details of all hotels displayed.

hotel

Details of each hotel

hotel-id

Id of the hotel

basic-info

Refer 'Hotel Info Response Description'.

room-rates

Object

--room-type

Room type code and description(Deluxe room, Executive room, Deluxe AC, etc). This field may not be unique.

--rate-breakdown

Breakdown of the fare rate( Base fare + Tax + etc)

--booking-code

The code that should to be passed as it is in the next 'Book call' (book_request.xml). This is an unique field to identify any booking.

provisional-booking-required

If this field is true, provisional booking step is mandatory. 

inclusions

Inclusions if any. Eg : All applicable taxes. Breakfast. Free stay for children under five (no bed). One way airport transfers

is-package

True if the rate belongs to DP, else False.

post-pay

True” if Pay at Hotel is available, else “False”.

is-special-rate

Optional field. "True” if the rate is a special/package rate, else “False”.

promo-offers

Object 

– offer-value

Description of the promo/offer

Error messages

Some error messages that you might get for an invalid search request. The HTTP response code in this case will be 400.

Error messageDescription
Not authorized to access the service API Key Header is missing or invalid.
Invalid value for parameter check-in Not a valid value for the parameter
Invalid value for parameter check-out Not a valid value for the parameter
Invalid value for parameter no-of-room Not a valid value for the parameter
Invalid value for parameter no-of-adults Not a valid value for the parameter
Please specify the city City is missing
Please specify the country Country is missing
Please specify the check-in date Check-in date is missing
Please specify the check-out date Check-out date is missing
Please specify valid date range Check-out date should be greater than Check-in date
Check-in date should be within 364 days Check-in date exceeds maximum possible booking date.
Please specify no-of-rooms No-of-rooms is missing
Please specify valid no-of-rooms Valid values are 1-4
Please specify adults-per-room Adults-per-room is missing. Valid adults per room is 1-4.
Number of adults-per-room does not match no-of-rooms This value should match the number of rooms in count, meaning if we request for 2 rooms, we need to specify 2 comma separated values for number_of_adults_per_room. viz: 1,2
Please specify children-per-room Children-per-room is missing. Valid children per room is 1-4.
Number of children-per-room does not match no-of-rooms This value should match the number of rooms in count, meaning if we request for 2 rooms, we need to specify 2 comma separated values for number_of_adults_per_room. viz: 1,2. Note that even if the number of children is Zero, this needs to be specified as well, viz: 0,0


Hotel info

The hotel info request takes the hotel ID as input and provides the detailed hotel information along with the thumbnail and wide-angle image URL in response.

Request details

Production URL:
http://www.cleartrip.com/places/hotels/info/{hotel Id}
Staging URL:
http://staging.cleartrip.com/places/hotels/info/{hotel Id} (basic authentication protected)
Method:
GET
Sample Request:
http://www.cleartrip.com/places/hotels/info/318327

Response details

Content type:
application/xml
Schema:
hotel_info.xsd
Sample XML:
Sample Hotel Info Response - Hotel Id:318327
Sample Hotel Info Response - Hotel Id:41020
Hotel Info Response Discription:

Name of the tag

 Descriptions

hotel-id

Id of the hotel

basic-info

Supplier name, Name and address of the hotel, rate info(high rate, low rate), communication info, hotel amenities and hotel ratings.

--hotel-info:rate-info

Rate Info Object 

--hotel-info:communication-info

Phone, fax and email details of the hotel.

--hotel-info:chain

The group which owns the hotel

--hotel-info:thumb-nail-image

 

--hotel-info:hotel-amenities

Availability of amenities such as Bar, Internet, Pool,Business center, Gym, etc..

--hotel-info:is-on-hold

“1” if 'hold booking' feature is available, else “O”

--hotel-info:hotel-ratings

 

 Hotel ratings object --hotel-info:hotel-rating

TA rating(out of 5.0), No. of user ratings

    --hotel-info:rating-detail

TA Rating of the hotel in different categories such as Location, Rooms, service, Value and Cleanliness.

        – hotel-info:rating-image-url

Image of 'TA rating' of the hotel.

--hotel-info:star-rating

Star rating of the hotel.

--hotel-info:ct-recommendation/

'True' if recommended by Cleartrip, else 'False'.

other-info

other info object 

--description

A detailed decription of the hotel.

--no. of rooms

No. of rooms in the hotel.

--facilities

Facilities such as Meeting Room, Banquet Hall, etc.if available in the hotel.

--room-info

The room type, room type code and amenities available in the room.

--restaurant

Description of the restaurants in the hotel.

--location info

Latitude, Longitude and Hotel driving directions.

--policy-info

Check-in, check-out times and cards accepted.

--image-info

The photos of the hotel.


Hotel policy

This call will return the cancellation policy and the allowed payment modes for booking a given hotel room.

Request details

Production URL:
https://api.cleartrip.com/hotels/1.0/policy
Staging URL:
http://api.staging.cleartrip.com/hotels/1.0/getRateRules
Method:
POST
Content type:
application/xml
Policy request schema details:
hotel_policy_request.xsd
Sample hotel policy request XML:
Sample Hotel Policy Request

The various elements of the rate rule policy request xml are described below:

Name Description Format Example
nri Whether the booking is made by/for an NRI Boolean true
hotel-id The search response returns a hotel-id along with each hotel found for the search criteria that was matched. The hotel-id of the hotel selected for booking should be passed here. Valid integer that was returned as a valid hotel-id in the search response. 41002
check-in-date See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2008-11-01
check-out-date See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2008-11-04
number-of-rooms See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2
adults-per-room See search request parameters for details. This should exactly the same value as that passed as part of the search request. 1,1
children-per-room See search request parameters for details. This should exactly the same value as that passed as part of the search request. 0,0
booking-code This value should be copied from the search response as-is. Valid alpha-numeric string as returned from the search response. :33719:26035:c:MAP:|M1_
room-type-code The room-type-code returned in the search response for the selected hotel and room-type. Valid alpha-numeric string as returned from the search response for the selected hotel and room-type. DBL-123

Response details

The response will contain the cancellation policy along with the payment modes supported for the book call.

Content type:
application/xml
Policy response schema details:
hotel_policy_response.xsd
Sample XML:
Sample Hotel Policy response
Hotel Policy Response Discription:

Name of the tag

 Descriptions

Cancel Policy

The cancellation policy of the hotel.

Payment modes

The modes of payment accepted by hotels.

Eg : Credit Card, Debit Card, etc.

Error messages

The possible error messages are similar to the book request messages.


Hotel Provisional Book

It is mandatory to use this api if 'provisional-booking-required' field is 'true' in search response xml. This api can be used by partners who take payment from the user at their end and then use deposit account to book the hotel from Cleartrip. But there can be scenarios where payment is taken from user and then booking fails because of unavailability. Using this api will eliminate that possibility. Card should be charged only if provisional booking is successful. If partners send the credit card details to Cleartrip and Cleartrip collects the payment then they can safely ignore this api. Cleartrip will do the provisional booking before charging the card.

Request details

Production URL:
https://api.cleartrip.com/hotels/1.0/provisionalbook
Staging URL:
http://api.staging.cleartrip.com/hotels/1.0/provisionalbook
Method:
POST
Content type:
application/xml
Request schema details:
provisional_book_request.xsd
Sample request XML:
Sample Provisional Book Request for search criteria 1 Room, 2 Adults, 0 Children, 2 Nights
Sample Provisional Book Request for search criteria 2 Rooms, 3 Adults, 1 Child, 2 Nights
Sample Provisional Book Request for search criteria 2 Rooms, 2 Adults, 3 Children, 2 Nights

The various elements of the rate rule provisional book request xml are described below:

Name Description Format Example
nri Whether the booking is made by/for an NRI Boolean true
hotel-id The search response returns a hotel-id along with each hotel found for the search criteria that was matched. The hotel-id of the hotel selected for booking should be passed here. Valid integer that was returned as a valid hotel-id in the search response. 41002
check-in-date See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2008-11-01
check-out-date See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2008-11-04
number-of-rooms See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2
adults-per-room See search request parameters for details. This should exactly the same value as that passed as part of the search request. 1,1
children-per-room See search request parameters for details. This should exactly the same value as that passed as part of the search request. 0,0
child-ages-per-room This is an optional field, which needs to be passed only if there are children selected in a room. If no-of-room selected is 2, then there should be 2 child-ages-per-room elements in the request. See the Sample XML for details.
age This is an optional field, which needs to be passed inside child-ages-per-room element, representing age of the child. If a room has 2 children, then there should be 2 age elements inside child-ages-per-room element each representing the age of the children belonging to that room. See the Sample XML for details.
booking-code This value should be copied from the search response as-is. Valid alpha-numeric string as returned from the search response. :33719:26035:c:MAP:|M1_
room-type-code The room-type-code returned in the search response for the selected hotel and room-type. Valid alpha-numeric string as returned from the search response for the selected hotel and room-type. DBL-123
customer Customer Information. See the Sample XML for details. The Customer Name should not contain any special characters and should be less than 50 characters. -

Response details

The response will contain the provisional booking id. This id has to be passed in book request. A valid response can contain empty string as provisional book id. In such cases please send an empty string as provisional book id in the book request.

Content type:
application/xml
Response schema details:
provisional_book_response.xsd
Sample XML:
Sample Provisional Book Response

Error messages

The possible error messages are similar to the book request messages.


Hotel Book

The booking system provides the ability to book a specified hotel room. Payment is required to book a hotel room using the Cleartrip hotel book API. Payment can be in the form of a credit card payment or a deposit account payment. Please refer to the API FAQ for further details regarding the payment options. API clients should ensure that the call made to the hotel book system is made over a secure SSL channel. Non-SSL requests for the book call will be rejected by the Cleartrip system. The booking response will contain the confirmation number or the specific error if the booking did not go through. For each transaction, if the payment mode is credit card, the card will be charged or if the payment mode is depost account, a debit entry will be made against the deposit account of the client user.

Request details

Production URL:
https://api.cleartrip.com/hotels/1.0/book
Staging URL:
http://api.staging.cleartrip.com/hotels/1.0/book
Method:
POST
Book request schema details:
book_request.xsd
Sample book request:
Sample book request XML

The various elements of the book request XML are described below:

Name Description Format Example
affiliate-txn-id If the API integrator wishes to track bookings done through Cleartrip API system using an ID specific to their local system, that ID can be passed in this field. Note that this ID can later be used to retrieve details of the trip. Valid alpha-numeric ASCII string ABCDEFG2134
nri Whether the booking is made by/for an NRI Boolean true
hotel-id The search response returns a hotel-id along with each hotel found for the search criteria that was matched. The hotel-id of the hotel selected for booking should be passed here. Valid integer that was returned as a valid hotel-id in the search response. 41002
check-in-date See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2008-11-01
check-out-date See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2008-11-04
number-of-rooms See search request parameters for details. This should exactly the same value as that passed as part of the search request. 2
number-of-room-nights Acutal number of room-nights requested including all rooms across all dates requested. In other words, if the search request was for 2 rooms for 2 nights, the room-nights value would be 2 * 2 = 4.

Note: the nights requested is not the arithmetic date difference between the check-in-date and check-out-date, it is one (1) less.

Valid integer. 4
adults-per-room See search request parameters for details. This should exactly the same value as that passed as part of the search request. 1,1
children-per-room See search request parameters for details. This should exactly the same value as that passed as part of the search request. 0,0
booking-code This value should be copied from the search response as-is. Valid alpha-numeric string as returned from the search response. :33719:26035:c:MAP:|M1_
room-type-code The room-type-code returned in the search response for the selected hotel and room-type. Valid alpha-numeric string as returned from the search response for the selected hotel and room-type. DBL-123
customer-ip-address The IP address of the caller. Valid IP address in dot format. 127.0.0.1
booking-amount This value should be calculated form the search response. This should be the total amount across number of rooms requested and number of nights requested for. This amount should also include taxes. If the total has a decimal, the amount should be rounded up to the next integer. Valid integer. 4000
customer Customer information. See the Sample xml for details.The Customer Name should not contain any special characters and should be less than 50 characters -
payment-type Should be the requested payment mode. CC for credit card payments and DA for deposit account payments DA or CC
id If payment mode is deposit account, the deposit account id of the client needs to be passed. This number is obtained at the time of registration. Please read the API FAQ for further details. Valid integer 123123
password Ignore - -
card-type-id If the payment mode is credit card, valid card-type-id should be passed.
  • 1 — Visa
  • 2 — MasterCard
  • 3 — AMEX
  • 4 — Citi Diners
Valid integer -
bank-id If the payment mode is credit card, this element can be ignored. - -
number If the payment mode is credit card, valid card number should be passed. Valid 16 digit credit card number -
expiration-month If the payment mode is credit card, valid expiration month of the credit card should be passed. Valid 2 digit integer 01-12. 08
expiration-year If the payment mode is credit card, valid expiration year of the credit card should be passed Valid 4 digit integer representing the year. 2011
card-id If the payment mode is credit card, the CVV found on the back of the card should be passed Valid Integer 353
name-on-card If the payment mode is credit card, the name on the card should be passed. Valid string Abcdefg Hijklm
provisional-book-id Optional element, it is the provisional book id returned in the provisional book response. This element will be present only if provisional book api is called. Valid string 123456

Response details

If the book request was successful, the response body returns an XML alongwith the HTTP status code 200. If any error is encountered during search, the response body will contain an XML with the root element error. See the schema and sample search result XML for more details. An invalid request will result in a HTTP response status code of 400.

Content type:
application/xml
Schema:
book-response.xsd
Sample XML:
Sample Hotel Book Response
Hotel Book Response Discription:

Name of the tag

 Descriptions

Confirmation number

The confirmation number for the booking.

Booking Id

The unique Id generated for the booking.

Error messages

Some error messages that you might get for an invalid search request. The HTTP response code in this case will be 400.

Error messageDescription
Not authorized to access the serviceAPI Key Header is missing or invalid.
Amount specified does not match actual booking amountThe calculated amount specified does not match the amount(s) sent back in the search response.
Invalid booking code specifiedBooking code specified does not match the code sent in the search response.
Cannot find the hotel specifiedHotel specified is not valid or there is no inventory left for the specified rate.
Cannot find the room specifiedRoom type specified is not valid or there is no inventory left for the specified room-type.
No access to deposit accountSpecified deposit account is invalid for the client user.


View itinerary

This call will reutrn the details of a given hotel booking. The input can either be the Cleartrip trip reference ID or the external transaction reference ID passed during booking by the client.

Request details

Production URL (using Cleartrip trip reference id):
https://api.cleartrip.com/hotels/1.0/trips/{cleartrip-trip-id}
Production URL (using affiliate trip reference id):
https://api.cleartrip.com/hotels/1.0/trips/ext/{affiliate-trip-id}
Staging URL (using Cleartrip trip reference id):
http://api.staging.cleartrip.com/hotels/1.0/trips/{cleartrip-trip-id}
Staging URL (using affiliate trip reference id):
http://api.staging.cleartrip.com/hotels/1.0/trips/ext/{affiliate-trip-id}
Method:
GET
Sample request URL
Sample request -
  • Using the cleartrip trip reference ID: https://api.cleartrip.com/hotels/1.0/trips/811141175
  • Using the external transaction reference ID: https://api.cleartrip.com/hotels/1.0/trips/ext/XXXXXX811141175

Response details

The response will contain the itinerary details of the hotel booking.

Content type:
application/xml
Schema:
Coming soon...
Sample XML:
Sample View Itinerary Response.
View Itinerary Response Discription:

Name of the tag

 Descriptions

trip ref

Cleartrip Booking Id.

check-in and check-out date

The check-in and check-out date for the booked trip.

room count

The no. of rooms booked.

hotel detail

Hotel Id, hotel name and address of the hotel booked.

room

The room type booked.

room rate

The pricing elements – break up of the fare.

booking info

 

-- booking status

The status of booking : Confirmed(P), Cancelled(Q), Refunded(K), etc..

-- voucher number

The ID of the voucher generated on successful booking.

contact detail

The contact details used for booking.

payment detail

The payment mode, amount paid and status.

Error messages

Some error messages that you might get for an invalid search request. The HTTP response code in this case will be 400.

Error messageDescription
Not authorized to access the serviceAPI Key Header is missing or invalid.
Trip for trip id xxx not found! Trip-ID XXX doesn’t exist. The HTTP status code sent will be 404 (Not Found) is returned with this error.

Hotel cancel

This call can be used for cancelling a previously booked hotel room. The service does not allow partial cancellations. The input to this will be the Cleartrip trip reference ID. Cancellation of a given trip will be allowed only if the user cancelling (identified by the API key sent in the HTTP header) is the same user who made the original booking.

Note: The cancellation charges that are returned in the response are indicative cancellation charges and the final charges may vary in some cases.

Request details

Production URL:
https://api.cleartrip.com/trips/hotel/{trip-id}
Staging URL:
http://api.staging.cleartrip.com/trips/hotel/{trip-id}
Method:
DELETE
Sample Request #1:
https://api.cleartrip.com/trips/hotel/XXXXXXXXX

Response details

Content type:
application/xml
Hotel cancel schema details:
hotel_cancel_response.xsd
Sample XML
Sample XML for a -
Hotel Cancel Response Discription:

Name of the tag

 Descriptions

txn-id

The transaction Id for cancellation.

refund amount

The amount refunded if cancellation is successful.

supplier-cancellation

“S” if cancellation is successful.

“F” if cancellation failed.

If the cancellation was attempted and it failed, the cancellation will be actioned manually and the API will NOT show the refund amount in the XML.

Error messages

Error messageDescription
200 (OK) Cancellation successful
400 (Bad Request) Requested URL invalid or incomplete
401 (Unauthorized) Incorrect or no API key found in header
403 (Forbidden) Cancellation not allowed due to violation of business rules or transaction rules
404 (Not Found) Requested resource not found
500 (Internal Server Error) Server encountered and internal error while attempting to process the request
501 (Not Implemented) Cancellation for this type of resource is not supported


Sample code

Hotel Search:
java, ruby, php
Hotel Book:
java, ruby, php
Hotel Policy:
java, ruby, php
View Itinerary:
java, ruby, php
Hotel Cancel:
java, ruby, php
Required Utlity (for java code):
java utility
Combined script (for ruby code):
ruby script

Notes: For using the java code, use your basic authentication username/password in utility.java and your API key in each of the requests. In case you are using the ruby code, ensure that the basic auhentication username, password and API key are entered in each of the requests.


Revision History

Version 1.0 :
  • Initial version
Version 1.1 :
  • Added Cancel API information.
  • Added Itinerary API information.
Version 1.2 :
  • Added alternate URLs information.
  • Added FAQ.
  • Added sample code in java,ruby.
  • Added cancel API response infomation.
Version 1.3 :
  • Changed the URLs for Retrieve Itinerary, Get Rate Rules, Cancel.
Version 1.4 :
  • Added description for responses.
  • Added multiple examples for requests and responses.
  • Added PHP sample codes.
  • Updated Java and Ruby sample codes.

Go to top