Request - Traveler's Name

The following is a sample of the schema for an Itinerary eBL request using a name. You can download the XSD files, which define the way in which the request should be structured.

To view the request sample without annotation, go to the unannotated version.

Explanation

Code

Begins the itinerary request.

<RetrieveTrip_RQ

Returns fare information. Use zero if you do not want fare information.

   AdditionalFareInfo="1"

Indicates the response will return a description of the passenger's air segment, if available.

   AdditionalAirSegmentInfo="1"

Indicates the response will return a description of the passenger's car segment, if available.

   AdditionalCarSegmentInfo="1"

Indicates the response will return a description of the passenger's hotel segment, if available.

   AdditionalHotelSegmentInfo="1"

Indicates the response will return a description of the passenger's W3 segment, if available.

   AdditionalW3SegmentInfo="1"

Indicates that the response will decode any information that was requested to be encoded.

   DecodeItems="true"

Indicates that the response will display the passenger's complete itinerary.

This is only applies when a customer supplies a session ID.

   DisplayItinerary="true">

Primary traveler's last name. See Response - Similar Names List to view a sample response with multiple traveler's names.

<PassengerLastName>jones</PassengerLastName>

Specifies the primary traveler's first name (optional).

<PassengerFirstName>tom</PassengerFirstName>

Ends the itinerary request.

</RetrieveTrip_RQ>