Travelfusion Direct Connect XML API > Post Booking APIs

Manage Booking API

Contents

Summary of Functionality (commands)

General Information and guidelines

XML Commands

ManageBookingAvailabilityPlane

StartManageBookingPlane

This API is used for modifying / adding ancillaries to an existing booking, e.g. luggage, insurance, seats, passenger details or travel class.

This document assumes the user is familiar with the Travelfusion Search and Book API.

This API is applicable to change options:

LUGGAGE
INSURANCE
SEATS
DETAILS
TRAVEL_CLASS
REDUCED_MOBILITY_ASSISTANCE
MEALS

The eligible bookings for manage must have one of the following statuses: Succeeded, BookingChangeSucceeded, CancelFailed.

Summary of Functionality (commands)

The Manage Booking API inherits both the same usage flow as in the Search and Book API and its XML structures. This document assumes the user is familiar with the Travelfusion Search and Book API. Also, it follows the same error handling guide as in every API under Travelfusion Direct Connect XML API.

The differences to the Search and Book API are the following. There is an additional API command, ManageBookingAvailabilityPlane, and instead of StartRouting users must use the StartManageBookingPlane command. This documentation emphasises on the new XML structures required by Manage Booking API. Below is a short description of the available API commands.

- ManageBookingAvailabilityPlane / retrieves (for a given supplier) the supported post-booking and authorisation / login options.
- StartManageBookingPlane / initiates a post-booking session (equivalent to StartRouting in standard search & book).
- CheckRouting / polls for StartManageBookingPlane result (equivalent to CheckRouting), the result contains the flight details of the booking.
- ProcessDetails / retrieves all possible post-booking options per traveller (equivalent to ProcessDetails).
- ProcessTerms / selects the required options and returns the final price of the post-booking change (equivalent to ProcessTerms).
- StartBooking / actions the post-booking change (equivalent to StartBooking).
- CheckBooking / polls for StartBooking result (equivalent to CheckBooking).

General Information and guidelines

Generally, the price elements returned by this API reflect the price of the modification / update / change / addition (i.e. how much it costs to apply the desired booking update). The price represents the cost of the update known to the API so far in the post-booking process; so for example, in CheckRouting the price may be zero, unlike ProcessTerms, where the price will be the full accurate price based on the selection of options.

The result of a booking update / change would be the creation of a new booking record (in the TF system, with new reference). For example, if a user makes a post-booking change on a TF booking with reference TFREFA, there would be a new TF booking record with reference TFREFB. Booking TFREFA becomes the parent of TFREFB (the child booking); in the end of a post-booking process, TFREFA would have the status of BookingChanged (from Succeeded), and TFREFB would be in status BookingChangeSucceeded. More information can be found in the Booking Change Statuses and Administration System sections of the Booking Changes guidelines.

XML Commands

This section contains a more detailed explanation of the API XML commands, including XML examples. For option DETAILS there is additional information with examples in Change Option DETAILS example Manage Booking flow.

ManageBookingAvailabilityPlane

The ManageBookingAvailabilityPlane command should be executed every time the user needs to perform a post-booking modification / update / change. This command must be cached on the user's side with a minimum timeout of 10 minutes. It provides all the necessary information the user needs in order to be able to proceed with a booking update:

- The change options that are available for the given supplier / airline.
- The log-in / authorisation information required by the airline.
- Various airline information, e.g. terms and conditions and so on.

REQUEST example

<XmlLoginId>XMLLOGINID</XmlLoginId>

<LoginId>LOGINID</LoginId>

<Supplier>airasiaarms</Supplier>

</ManageBookingAvailabilityPlane>

</CommandList>

RESPONSE example

<LoginId>LOGINID</LoginId>

<Supplier>airasiaarms</Supplier>

<ChangeOptions>LUGGAGE|SEATS|DETAILS</ChangeOptions>

<Name>TF_BOOKING_REFERENCE</Name>

<DisplayText>Travelfusion Booking reference</DisplayText>

</AuthOptionItem>

</AuthOptionItemList>

</AuthOption>

<Name>BOOKING_REFERENCE</Name>

<DisplayText>Booking reference</DisplayText>

</AuthOptionItem>

</AuthOptionItemList>

</AuthOption>

</AuthOptionList>

<DisplayName>LUGGAGE Terms and Conditions</DisplayName>

<Info>Should you wish to upgrade from a 20kg checked baggage to 25kg or more, this can be done up to 4 hours prior to scheduled departure time or even at the airport check-in counter. * Each guest can purchase up to 40kg per way, per person. Should you have 40kg or more of checked baggage, we recommend that each checked baggage should not exceed 32kg. * Any guest exceeding their personal checked baggage allowance will be charged for excess baggage at the prevailing rate on the day of travel. Excess baggage charges are quoted and billed in the departure country?s currency.</Info>

</SupplierInfo>

<DisplayName>SEATS Terms and Conditions</DisplayName>

<Info>Some sample text here.</Info>

</SupplierInfo>

</SupplierInfoList>

</DetailList>

</ManageBookingAvailabilityPlane></CommandList>

- <ChangeOptions> a pipe-separated list of supported post-booking options. Each option defines which of the post-booking APIs the user should continue with:

OUT_DATE|RET_DATE|ORIGIN|DESTINATION - use Booking Changes API.
LUGGAGE|INSURANCE|SEATS|DETAILS|TRAVEL_CLASS|REDUCED_MOBILITY_ASSISTANCE|MEALS - use Manage Booking API.
CANCEL - use Cancellations API.

- <AuthOptionList> a list of possible options / ways required to log in to the supplier / airline system. It contains one or more options. The user must select one of the options in this list to submit with values in the next step, StartManageBookingPlane.

-- <AuthOption> contains one or more parameters required to log in to the supplier / airline system.

- <SupplierInfoList> see in standard search & book CheckRouting response.

- <DetailList> this element is present when the DETAILS option is in <ChangeOptions>. It specifies all possible flight, passenger or generally booking related details that may be modified.

- <Detail> specifies the booking detail that can be changed. It contains the Name attribute having a self-documenting text value of what the detail is about and the PerPassenger attribute having a boolean value denoting if this detail change applies per passenger or on the entire booking. Below is a list of all possible Name values.

FullName

FirstNameAndLastName

FirstName

TitleAndFirstName

LastName

Title

DateOfBirth

Nationality

Email

HomePhone

BookingMobilePhone

WorkPhone

PassportNumber

PassportExpiryDate

PassportCountryOfIssue

FixedDetailsChangeCharge

For more information please refer to Change Option DETAILS example Manage Booking flow.

StartManageBookingPlane

The StartManageBookingPlane command initiates a post-booking session; it produces a <RoutingId> that uniquely identifies this post-booking change session. It is the equivalent to StartRouting in standard search & book, with the difference being, only the elements shown in the following example are required.

REQUEST example

<XmlLoginId>XMLLOGINID</XmlLoginId>

<LoginId>LOGINID</LoginId>

<Mode>Plane</Mode>

<Supplier>airasiaarms</Supplier>

<Name>BOOKING_REFERENCE</Name>

</AuthOptionItem>

</AuthOptionItemList>

</AuthOption>

<Supplier>airasiaarms</Supplier>

<Name>UserLogin</Name>

<Value>USERVALUE</Value>

</CustomSupplierParameter>

<Supplier>airasiaarms</Supplier>

<Name>UserPassword</Name>

<Value>PASSVALUE</Value>

</CustomSupplierParameter>

</CustomSupplierParameterList>

</BookingProfile>

</StartManageBookingPlane>

</CommandList>

- <TFBookingReference> is optional. If provided, it is the equivalent of using <AuthOptionItem> TF_BOOKING_REFERENCE which is deprecated, therefore users are advised to use <TFBookingReference> element.

- <AuthOption> contains the input values for the parameters required to log in to the supplier / airline system. The user must input here an option selected from those listed in the previous step, in ManageBookingAvailabilityPlane response.

All other XML elements are described as in StartRouting Request specification.

RESPONSE example

<LoginId>LOGINID</LoginId>

<RoutingId>Z1RL63H6CNXONXL2</RoutingId>

<Supplier>airasiaarms</Supplier>

<Url>http://www.airasia.com/</Url>

</Vendor>

<Complete>false</Complete>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

</RequestedLocations>

</Router>

</RouterList>

<Name>Changi International Airport</Name>

<Name>Singapore</Name>

</Country>

<Type>Airport</Type>

<City>

<Name>Singapore</Name>

</City>

<Name>Changi International Airport</Name>

</Airport>

</Location>

</Origin>

<Name>Kuala Lumpur International Airport</Name>

<Name>Malaysia</Name>

</Country>

<Type>Airport</Type>

<City>

<Name>Kuala Lumpur</Name>

</City>

<Name>Kuala Lumpur International Airport</Name>

</Airport>

</Location>

</Destination>

</Summary>

</StartManageBookingPlane>

</CommandList>

The XML elements are described as in StartRouting Response specification.

CheckRouting

The CheckRouting command polls for StartManageBookingPlane result. The CheckRouting may need to be called more than once for the same session (RoutingId). Please check with CheckRouting that describes how to use it and when to stop polling. The CheckRouting response contains the flight details of the booking.

REQUEST example

<XmlLoginId>XMLLOGINID</XmlLoginId>

<LoginId>LOGINID</LoginId>

<RoutingId>Z1RL63H6CNXONXL2</RoutingId>

</CheckRouting>

</CommandList>

The XML elements are described as in CheckRouting Request specification.

RESPONSE example

<LoginId>LOGINID</LoginId>

<RoutingId>Z1RL63H6CNXONXL2</RoutingId>

<Mode>plane</Mode>

<Supplier>airasiaarms</Supplier>

<Url>http://www.airasia.com/</Url>

</Vendor>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

</RequestedLocations>

<Group>

<Id>ELBHDRMXTDRX27OH</Id>

</CacheInfo>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

...

</FlightId>

<TfClass>Economy With Restrictions</TfClass>

<SupplierClass>Regular</SupplierClass>

</TravelClass>

<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>

</Segment>

</SegmentList>

</Outward>

</OutwardList>

<Id>EWY74ZJWCF2VOQ9I</Id>

</CacheInfo>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

...

</FlightId>

<TfClass>Economy With Restrictions</TfClass>

</TravelClass>

<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>

</Segment>

</SegmentList>

</Return>

</ReturnList>

<Price>

<Name>Manage Booking Charge</Name>

</TaxItem>

</TaxItemList>

</Price>

</Group>

</GroupList>

</Router>

</RouterList>

...

</Summary>

</CheckRouting>

</CommandList>

The XML elements are described as in CheckRouting Response specification.

ProcessDetails

The purpose of ProcessDetails is to retrieve all possible post-booking update options per traveller and show them to the user. It is equivalent to ProcessDetails, however, the response includes an additional element, <ManagedTravellerList>.

REQUEST example

<XmlLoginId>XMLLOGINID</XmlLoginId>

<LoginId>LOGINID</LoginId>

<RoutingId>Z1RL63H6CNXONXL2</RoutingId>

<OutwardId>ELBHDRMXTDRX27OH</OutwardId>

<ReturnId>EWY74ZJWCF2VOQ9I</ReturnId>

</ProcessDetails>

</CommandList>

The XML elements are described as in ProcessDetails Request specification.

RESPONSE example

<LoginId>LOGINID</LoginId>

<RoutingId>Z1RL63H6CNXONXL2</RoutingId>

<Name>CardSecurityNumber</Name>

<Type>notice</Type>

<PerPassenger>false</PerPassenger>

<IsOptional>false</IsOptional>

</RequiredParameter>

<Name>ChildrenAndInfantsSearch</Name>

<Type>notice</Type>

<PerPassenger>false</PerPassenger>

</RequiredParameter>

<Name>ChildrenAndInfantsBooking</Name>

<Type>notice</Type>

<PerPassenger>false</PerPassenger>

</RequiredParameter>

<Name>BookingSourceRef</Name>

<Type>custom</Type>

<PerPassenger>false</PerPassenger>

</RequiredParameter>

</RequiredParameterList>

<Supplier>airasiaarms</Supplier>

<Url>http://www.airasia.com/</Url>

</Vendor>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

</RequestedLocations>

<Group>

<Id>394E77UD6EJOEEOM</Id>

<Id>ELBHDRMXTDRX27OH</Id>

</CacheInfo>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

...

</FlightId>

<TfClass>Economy With Restrictions</TfClass>

<SupplierClass>Regular</SupplierClass>

</TravelClass>

<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>

</Segment>

</SegmentList>

</Outward>

</OutwardList>

<Id>EWY74ZJWCF2VOQ9I</Id>

</CacheInfo>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

...

</FlightId>

<TfClass>Economy With Restrictions</TfClass>

</TravelClass>

<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>

</Segment>

</SegmentList>

</Return>

</ReturnList>

<Price>

<Name>Manage Booking Charge</Name>

</TaxItem>

</TaxItemList>

</Price>

</Group>

</GroupList>

</Router>

</SupplierHandoffData>

<Name>

</NamePartList>

</Name>

<TravellerType>Adult</TravellerType>

</SupplierTravellerInfo>

<DisplayName>Gender</DisplayName>

</SupplierTravellerInfo>

</SupplierTravellerInfoList>

<Name>MealType</Name>

<Type>value_select</Type>

<DisplayText>Please Select a Meal Type: 700-RCCB(Roast Chicken with BBQ Sauce@4.00SGD), 700-NLCB(Pak Nasser nasi lemak@4.00SGD), 700-CRCB(Chicken Rice of Uncle Chin@4.00SGD); 701-RCCB(Roast Chicken with BBQ Sauce@4.00SGD), 701-NLCB(Pak Nasser nasi lemak@4.00SGD), 701-CRCB(Chicken Rice of Uncle Chin@4.00SGD);</DisplayText>

</RequiredParameter>

<Name>SeatOptions</Name>

<Type>custom</Type>

<DisplayText>Please Select Seat Options: 700-1C(A|K|LA|EL|@18.90SGD@), 700-1D(A|K|LA|EL|@18.90SGD@), 700-1E(K|LA|EL|N|@18.90SGD@), 700-1F(K|LA|EL|W|@18.90SGD@), 700-2A(W|@15.90SGD@), 700-2B(N|@15.90SGD@), 700-2C(A|@15.90SGD@), 700-2D(A|@15.90SGD@), 700-2E(N|@15.90SGD@), 700-2F(W|@15.90SGD@), ...</DisplayText>

</RequiredParameter>

<Name>OutwardLuggageOptions</Name>

<Type>value_select</Type>

<DisplayText>Please Select Outward Luggage Option: 1 (1 bags - 25Kg total - 0.00 SGD), 2 (1 bags - 30Kg total - 23.00 SGD), 3 (2 bags - 40Kg total - 45.00 SGD)</DisplayText>

</RequiredParameter>

<Name>ReturnLuggageOptions</Name>

<Type>value_select</Type>

<DisplayText>Please Select Return Luggage Option: 1 (1 bags - 30Kg total - 0.00 SGD), 2 (2 bags - 40Kg total - 22.00 SGD)</DisplayText>

</RequiredParameter>

</RequiredParameterList>

</ManagedTraveller>

<Name>

</NamePartList>

</Name>

<TravellerType>Child</TravellerType>

</SupplierTravellerInfo>

<DisplayName>Gender</DisplayName>

</SupplierTravellerInfo>

</SupplierTravellerInfoList>

<Name>MealType</Name>

<Type>value_select</Type>

<DisplayText>Please Select a Meal Type: 700-RCCB(Roast Chicken with BBQ Sauce@4.00SGD), 700-NLCB(Pak Nasser nasi lemak@4.00SGD), 700-CRCB(Chicken Rice of Uncle Chin@4.00SGD); 701-RCCB(Roast Chicken with BBQ Sauce@4.00SGD), 701-NLCB(Pak Nasser nasi lemak@4.00SGD), 701-CRCB(Chicken Rice of Uncle Chin@4.00SGD);</DisplayText>

</RequiredParameter>

<Name>SeatOptions</Name>

<Type>custom</Type>

<DisplayText>Please Select Seat Options: 700-1C(A|K|LA|EL|@18.90SGD@), 700-1D(A|K|LA|EL|@18.90SGD@), 700-1E(K|LA|EL|N|@18.90SGD@), 700-1F(K|LA|EL|W|@18.90SGD@), 700-2A(W|@15.90SGD@), 700-2B(N|@15.90SGD@), 700-2C(A|@15.90SGD@), 700-2D(A|@15.90SGD@), 700-2E(N|@15.90SGD@), 700-2F(W|@15.90SGD@), ...</DisplayText>

</RequiredParameter>

<Name>OutwardLuggageOptions</Name>

<Type>value_select</Type>

<DisplayText>Please Select Outward Luggage Option: 1 (1 bags - 25Kg total - 0.00 SGD), 2 (1 bags - 30Kg total - 23.00 SGD), 3 (2 bags - 40Kg total - 45.00 SGD)</DisplayText>

</RequiredParameter>

<Name>ReturnLuggageOptions</Name>

<Type>value_select</Type>

<DisplayText>Please Select Return Luggage Option: 1 (1 bags - 20Kg total - 22.00 SGD), 2 (1 bags - 25Kg total - 25.00 SGD), 3 (1 bags - 30Kg total - 48.00 SGD), 4 (2 bags - 40Kg total - 70.00 SGD)</DisplayText>

</RequiredParameter>

</RequiredParameterList>

</ManagedTraveller>

</ManagedTravellerList>

<CardType>Visa Credit</CardType>

</Charge>

<ChargeIsPerPassengerLeg>false</ChargeIsPerPassengerLeg>

</CardCharge>

</RoundingPolicy>

</SupportedCard>

...

</SupportedCardList>

</ProcessDetails>

</CommandList>

The XML elements are described as in ProcessDetails Response specification.

- <ManagedTravellerList> contains the list of managed travellers for this booking.

-- <ManagedTraveller> contains information about a managed traveller.

--- <Name> the traveller’s name. It may follow the General Name Format specification.

--- <TravellerType> contains one of the following values: Senior, Adult, Youth, Student, Child, Infant.

--- <Age> the age of the traveller. If the age / DOB is not available from the airline, then the API sets it with a predefined value depending on the type, e.g. 30 for Adult, 8 for Child, and so on...

--- <SupplierTravellerInfoList> contains a list of items of information about the traveller. It usually is additional free text information (with no particular structure or syntax rules) provided by the supplier. The API user may (or not) decide to use this in their implementation.

--- <RequiredParameterList> a list of parameters (with available options) that need to be submitted (within the booking profile) in the following step, ProcessTerms. The specification of <RequiredParameterList> can be found in the CheckRouting Response specification. Please refer to the Custom Supplier Parameters Guide to understand how to handle these parameters.

ProcessTerms

The ProcessTerms command is used to submit and select the traveller details and required booking update / change options respectively (equivalent to ProcessTerms, also see the XML Bookings and Handling Guide); it returns the final price of the post-booking change.

REQUEST example

<XmlLoginId>XMLLOGINID</XmlLoginId>

<LoginId>LOGINID</LoginId>

<Mode>plane</Mode>

<RoutingId>Z1RL63H6CNXONXL2</RoutingId>

<Name>

</NamePartList>

</Name>

<Name>OutwardLuggageOptions</Name>

</CustomSupplierParameter>

</CustomSupplierParameterList>

</Traveller>

<Name>

</NamePartList>

</Name>

<Name>OutwardLuggageOptions</Name>

</CustomSupplierParameter>

</CustomSupplierParameterList>

</Traveller>

</TravellerList>

<Name>

</NamePartList>

</Name>

<BuildingName>Dean's Court</BuildingName>

<Street>St. Georges Road</Street>

<Locality>Clifton</Locality>

<City>Bristol</City>

</Address>

</MobilePhone>

<Email>john.doe.1234@gmail.com</Email>

</ContactDetails>

<Name>

</NamePartList>

</Name>

<BuildingName>Dean's Court</BuildingName>

<Street>St. Georges Road</Street>

<Locality>Clifton</Locality>

<City>Bristol</City>

</Address>

</NamePartList>

</NameOnCard>

<Number>CARDNUMBER</Number>

<CardType>MasterCard</CardType>

</CreditCard>

</BillingDetails>

</BookingProfile>

</ProcessTerms>

</CommandList>

The XML elements are described as in ProcessTerms Request specification.

- <TravellerList> the order of the travellers in this list must be exactly as found in the <ManagedTravellerList> in ProcessDetails response in the previous step.

- <ContactDetails> is optional. For TF bookings, the API will use the contact details from the existing TF booking record or the supplier / airline if exist.

- <BillingDetails> can be omitted if the user of this API is set up with TF Pay.

RESPONSE example

<LoginId>LOGINID</LoginId>

<RoutingId>Z1RL63H6CNXONXL2</RoutingId>

<TFBookingReference>Z999DHBMW</TFBookingReference>

<Name>CardSecurityNumber</Name>

<Type>notice</Type>

<PerPassenger>false</PerPassenger>

<IsOptional>false</IsOptional>

</RequiredParameter>

<Name>ChildrenAndInfantsSearch</Name>

<Type>notice</Type>

<PerPassenger>false</PerPassenger>

</RequiredParameter>

<Name>ChildrenAndInfantsBooking</Name>

<Type>notice</Type>

<PerPassenger>false</PerPassenger>

</RequiredParameter>

<Name>BookingSourceRef</Name>

<Type>custom</Type>

<PerPassenger>false</PerPassenger>

</RequiredParameter>

</RequiredParameterList>

<Supplier>airasiaarms</Supplier>

<Url>http://www.airasia.com/</Url>

</Vendor>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

</RequestedLocations>

<Group>

<Id>394E77UD6EJOEEOM</Id>

<Id>ELBHDRMXTDRX27OH</Id>

</CacheInfo>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

...

</FlightId>

<TfClass>Economy With Restrictions</TfClass>

<SupplierClass>Regular</SupplierClass>

</TravelClass>

<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>

</Segment>

</SegmentList>

</Outward>

</OutwardList>

<Id>EWY74ZJWCF2VOQ9I</Id>

</CacheInfo>

<Type>airport</Type>

</Origin>

<Type>airport</Type>

</Destination>

...

</FlightId>

<TfClass>Economy With Restrictions</TfClass>

</TravelClass>

<SegmentMayEndWithAStop>false</SegmentMayEndWithAStop>

</Segment>

</SegmentList>

</Return>

</ReturnList>

<Price>

<Name>Manage Booking Charge</Name>

</TaxItem>

<Name>Luggage surcharge</Name>

</TaxItem>

</TaxItemList>

</Price>

</Group>

</GroupList>

</Router>

</ProcessTerms>

</CommandList>

The XML elements are described as in ProcessTerms Response specification.

StartBooking

The StartBooking executes the post-booking update / change on the supplier / airline (equivalent to StartBooking; also see the XML Bookings and Handling Guide, however, 'Fake' Bookings functionality is not supported at the moment).

REQUEST example

<XmlLoginId>XMLLOGINID</XmlLoginId>

<LoginId>LOGINID</LoginId>

<TFBookingReference>Z99DOHBMW</TFBookingReference>

</ExpectedPrice>

</StartBooking>

</CommandList>

The XML elements are described as in StartBooking Request specification.

RESPONSE example

<LoginId>LOGINID</LoginId>

<TFBookingReference>Z99DOHBMW</TFBookingReference>

</StartBooking>

</CommandList>

The XML elements are described as in StartBooking Response specification.

CheckBooking

The CheckBooking command polls for StartBooking result (equivalent to CheckBooking). The change / post-booking process follows the same process as in the Booking Process shown in the XML Bookings and Handling Guide.

The post-booking change status changes follow the same rules as in Booking Change Statuses, as shown in the Booking Changes Guidelines; the same applies for the Administration System.

REQUEST example

<XmlLoginId>XMLLOGINID</XmlLoginId>

<LoginId>LOGINID</LoginId>

<TFBookingReference>Z99DOHBMW</TFBookingReference>

</CheckBooking>

</CommandList>

The XML elements are described as in CheckBooking Request specification.

RESPONSE example

<LoginId>LOGINID</LoginId>

<TFBookingReference>Z99DOHBMW</TFBookingReference>

<Status>BookingChangeSucceeded</Status>

</CheckBooking>

</CommandList>

The XML elements are described as in CheckBooking Response specification.

Subpages (1): Change Option DETAILS example Manage Booking flow