Travelfusion Direct Connect XML API > Guidelines >

Hotel Booking API

This guide is designed to give a quick start to your integration with the Travelfusion Hotel Booking API. In the XML examples below, various XML elements and attributes have been omitted for simplicity. There are also many more details, features and functions available that you can read about in our XML Request and Reponse Specifications. These specifications also set out specific guidelines concerning how the API should be used and gives various other information that should be read before your integration is completed and released to end users.

The Hotel Booking API provides the following stages:

Details - Select hotel option and get complete information about a hotel

Terms - Submit booking profile (traveller, contact, billing details)

Booking - Commit a booking request

Cancel - Commit a cancellation request

Users may implement the above stages by submiting a number of requests (or commands) to the API in order, as shown in the table below. This table provides a summary; more detailed information is given further in this document.

The above commands are explained in detail below.

Step 1: StartDetailsHotel

Once the end user has decided which hotel option they would like to book, a The StartDetailsHotel request should be made to begin the booking process. Multiple requests of this type can be initiated in order to get details of different hotels in the results. However, the Terms stage will initiate a booking for the lastly selected option in this stage. The optional HandoffParametersOnly element must be ommitted or set to false; otherwise, the user will receive a handoff URL.

Request (xml spec detail)

<StartDetailsHotel>

<OptionId>JBWXSLTXSCBLWKRJ</OptionId>

<ExtraId>CQK7ZSQPHF40DA74</ExtraId>

</RoomExtra>

</RoomExtraList>

<HandoffParametersOnly>false</HandoffParametersOnly>

</StartDetailsHotel>

</CommandList>

The StartDetailsHotel response may normally be ignored.

Response (xml spec detail.)

<StartDetailsHotel millis="1">

<OptionId>JBWXSLTXSCBLWKRJ</OptionId>

</StartDetailsHotel>

</CommandList>

Step 2: CheckDetailsHotel

The CheckDetailsHotel request retrieves the result of the previous (StartDetailsHotel) request.

Request (xml spec detail)

<CheckDetailsHotel>

<OptionId>JBWXSLTXSCBLWKRJ</OptionId>

</CheckDetailsHotel>

</CommandList>

The response may contain an updated Router element with required parameters (like whether date of birth is required per traveller, etc. see a list of hotel parameters here), extra supplier information (terms, credit card requirements, etc.), list of room extras for each room within an option and possibly a supported payment card list (if supplied at this stage).

Once the response contains an updated router, no futher polling will be accepted for the selected hotel. If, subsequently, details for the same hotel are required, users must start over with a new StartDetailsHotel request.

Response (xml spec detail)

<CheckDetailsHotel millis="0">

<PerRoom>false</ PerRoom>

<Name>DateOfBirth</Name>

<DisplayText>Date of birth (dd/mm/yyyy)</DisplayText>

<IsOptional>false</IsOptional>

</RequiredParameter>

<PerRoom>false</ PerRoom>

<Name>DateOfBirthIsNotRequiredForAdults</Name>

</RequiredParameter>

<PerRoom>true</ PerRoom> // required per room

<Name>GuestName</Name>

<PerPassenger>false</PerPassenger>

<IsOptional>false</IsOptional>

</RequiredParameter>

...

</RequiredParameterList>

...

...

</ResultList>

<DisplayName>credit Card as guarantee,not charged</DisplayName>

<Info>the room will be hold the whole night. booking requires a credit card as guarantee, there might be cancellation fees.</Info>

</SupplierInfo>

<DisplayName>no credit card as guarantee</DisplayName>

<Info>the customer has to arrive until 6 p.m., at booking time no guarantee like credit card is required, cancellation can be made until 6 p.m. of the arrival day, a cancellation is actually not required.</Info>

</SupplierInfo>

...

<DisplayName>Terms and conditions</DisplayName>

<Info>https://www.hrs.com/web3/showCmsPage.do?clientId=ZW5fX05FWFQ-&cid=3-2&pageId=conditions&noBack=true</Info>

</SupplierInfo>

</SupplierInfoList>

</Router>

...

</SupplierHandoffData>

...

</SupportedCardList>

</CheckDetailsHotel>

</CommandList>

Step 3: StartTermsHotel

The StartTermsHotel request is used to submit the traveller(s), contact and billing details for this booking.

Request (xml spec detail)

<StartTermsHotel>

<Supplier>hotelreservationservice</Supplier>

<Name>AgentLogin</Name>

<Value>jimbo</Value>

</CustomSupplierParameter>

</CustomSupplierParameterList>

<Name>

<NamePart>Peterson</NamePart>

</NamePartList>

</Name>

<Name>DateOfBirth</Name>

</CustomSupplierParameter>

</CustomSupplierParameterList>

</Traveller>

</TravellerList>

<Name>

<NamePart>Peterson</NamePart>

</NamePartList>

</Name>

<Company>TravelFusion</Company>

<BuildingName>Dean's Court</BuildingName>

<Street>St. Georges Road</Street>

<Locality>Clifton</Locality>

<City>Bristol</City>

</Address>

</HomePhone>

</WorkPhone>

</MobilePhone>

<Fax>

</Fax>

<Email>andy@hotmail.com</Email>

</ContactDetails>

<Name>

<NamePart>Peterson</NamePart>

</NamePartList>

</Name>

<Company>TravelFusion</Company>

<BuildingName>Dean's Court</BuildingName>

<Street>St. Georges Road</Street>

<Locality>Clifton</Locality>

<City>Bristol</City>

</Address>

<Company>Travelfusion</Company>

<NamePart>Mr Andy S Peterson</NamePart>

</NamePartList>

</NameOnCard>

<CardType>MasterCard</CardType>

</CreditCard>

</BillingDetails>

</BookingProfile>

</StartTermsHotel>

</CommandList>

The response will contain a TFBookingReference element. This is the Travelfusion booking reference for this booking. Note that the booking is not actually executed until the StartHotelBooking request is submitted.

Response (xml spec detail)

<StartTermsHotel millis="271">

</StartTermsHotel>

</CommandList>

Step 4: CheckTermsHotel

The CheckTermsHotel request retrieves the result of the previous (StartTermsHotel) request.

Request (xml spec detail)

<CheckTermsHotel>

</CheckTermsHotel>

</CommandList>

The response may contain an updated Router element with required parameters (like whether date of birth is required per traveller, etc.), extra supplier information (terms, credit card requirements, etc.), and possibly a supported payment card list (if supplied at this stage). A Router element is also returned which will contain any new data related to the hotel option / price. The value of Status element indicates the status of the Terms stage.

TermsInProgress - User must re-submit CheckTermsHotel request until the status changes. The delay between resubmissions should be at least 2 seconds.

TermsFailed - User can no longer proceed with booking process

TermsSucceeded - User can proceed in the next stage and continue with booking process

Response (xml spec detail)

<CheckTermsHotel millis="36">

<Status>TermsSucceeded</Status>

<PerRoom>false</ PerRoom>

<Name>DateOfBirth</Name>

<DisplayText>Date of birth (dd/mm/yyyy)</DisplayText>

<IsOptional>false</IsOptional>

</RequiredParameter>

...

</RequiredParameterList>

...

...

</ResultList>

<DisplayName>Terms and conditions</DisplayName>

<Info>https://www.hrs.com/web3/showCmsPage.do?clientId=ZW5fX05FWFQ-&cid=3-2&pageId=conditions&noBack=true</Info>

</SupplierInfo>

...

</SupplierInfoList>

</Router>

</CheckTermsHotel>

</CommandList>

Step 5: StartBookingHotel

The StartBookingHotel request is used to initiate the booking. The FakeBooking element is required for development purposes only. If FakeBooking is omitted or set to false, a real booking will be made.

Request (xml spec detail)

<StartBookingHotel>

<EnableFakeBooking>false</EnableFakeBooking>

<FakeBookingStatus>Succeeded</FakeBookingStatus>

</FakeBooking>

</StartBookingHotel>

</CommandList>

Response (xml spec detail)

<StartBookingHotel millis="56">

</StartBookingHotel>

</CommandList>

Step 6: CheckBookingHotel

The CheckBookingHotel request retrieves the result of the previous (StartBookingHotel) request.

Request (xml spec detail)

<CheckBookingHotel>

</CheckBookingHotel>

</CommandList>

The CheckBookingHotel response contains the latest status of the booking.

Response (xml spec detail)

<CheckBookingHotel millis="27">

<Status>Succeeded</Status>

</CheckBookingHotel>

</CommandList>

Step 7: StartBookingCancelHotel

Initiates a booking cancellation request. It requires the TF booking reference. Please note - we strongly advise that you check the terms and conditions of the booking you wish to cancel, before cancelling it. You can do that using the GetBookingDetails command (see GetBookingDetails request and response).

Request (xml spec detail)

<StartBookingCancelHotel>

</StartBookingCancelHotel>

</CommandList>

The CheckBookingHotel response contains the latest status of the booking.

Response (xml spec detail)

<StartBookingCancelHotel>

</StartBookingCancelHotel>

</CommandList>