<Order>
|
Order to be created.
Specifying individual Order Item Sets and their associated Offer Item(s).
|
M |
<OrderItem>
|
Used for selling by value (long sells).
This should be repeated per pax type for flight items. If you have 2 x ADT, 2 x CHD and 2 x INF then OfferItem must be specified three times. One each for ADT, CHD and INF for flight items
For young adult passengers, a separate OfferItem should be specified for flight items. Similarly, OfferItem must be repeated for each seat item being purchased. If you have 2 x ADT, 2 x CHD and 2 x INF and all are buying seats then OfferItem must be specified six times one each for each passenger and seat
Also, OfferItem should be repeated for all the passenger who wants to buy the additional bags per OriginDestination
|
M |
<OfferItemID>
|
The airline-assigned unique Offer Item ID. Pass a unique number for each OfferItem
Example: 1
|
M |
Owner attr
|
Always pass “BA” |
M |
<OfferItemType>
|
Offer Item Type.
OfferItem for all passengers of the same type.
|
M |
<DetailedFlightItem>
|
Flight offer item |
M |
refs (Attribute)
|
Reference to passengers to whom the flight item is specified. The passenger reference should be the same as what was defined in
PassengerLists
.
If this flight item is applicable for 2 passengers then refs should be T1 and T2 separated by a space
Example: T1 T2
|
M |
<Price>
|
Flight pricing details (fare and tax) for one passenger of the pax type
This must be the same as what was returned in the OfferPrice response. The total fare and total tax are compared against the total fare and total tax returned during the booking process and if the price doesn’t match an error is returned.
|
M |
<BaseAmount>
|
This is the total fare for one passenger of the passenger type. This must be the same as what was returned in the OfferPrice response
Example: 266
|
M |
Code attr
|
|
M |
<Taxes>
|
Ticket Tax/fee/charge details to indicate taxes that apply to the country of commencement of travel and routing |
M |
<Total>
|
This is the total tax for one passenger of the passenger type. This must be the same as what was returned in the
OfferPrice
response
Example: 373
|
M |
<OriginDestination>
|
Origin and destination (O&D) details. This must be repeated for each O&D. If the request is for EDI-AMS return then this must be repeated twice once for EDI-AMS and once for AMS-EDI.
This element can accept up to 6 Origin-Destination pairs
|
M |
<Flight>
|
List of flights within an O&D. If the request is for EDI-AMS return with each O&D containing 2 flights (EDILHR and LHRAMS; AMSLHR and LHREDI) then for each O&D Flight should be repeated twice once for EDILHR and once for LHRAMS |
M |
<SegmentKey>
|
Unique flight segment key
Example: F1
This key will be used to associate seat item on a flight. Specify this key only for the first DetailedFlightItem, as the flight items are the same for all passengers
This must be passed if the request includes SeatItems (i.e customer wants to buy flights and seats).
|
O |
<Departure>
|
Departure (origin) Airport, Date and Time information. |
M |
<AirportCode>
|
Departure airport IATA code
Example: LHR |
M |
<Date>
|
Local Departure date i.e. local to the departure location
Example: 2015-08-13 |
M |
<Time>
|
Local Departure time i.e. local to the departure location
Example: 08:30 |
|
<Arrival>
|
Arrival information |
M |
<AirportCode>
|
Arrival airport IATA code
Example: AMS |
M |
<Date>
|
Local Arrival date i.e. local to the arrival location
Example: 2015-08-19
|
O |
<Time>
|
Local Arrival time i.e. local to the arrival location
Example: 11:10
|
O |
<MarketingCarrier>
|
Marketing Carrier information.
This is the carrier that sells with its own code as part of a codeshare agreement on a flight that is actually operated by another carrier.
|
M |
<AirlineID>
|
Marketing carrier code
Example: BA |
M |
<Name>
|
Airline Name.
Example: British Airways |
|
<FlightNumber>
|
Marketing flight number
Example: 1403
|
M |
<ClassOfService>
|
Selling or booking class details
|
M |
refs attr
|
Reference to a fare basis code for the passenger type applicable for this OfferItem
Example:
FBCODE1ADT
FBCODE1CHD
FBCODE1INF
- The service expects the client to provide fare basis code in OrderCreateRQ in order to quote correct fare product
- It is recommended that the same reference returned in
OfferPriceRS
is provided in OrderCreateRQ
|
M |
<Code>
|
Selling class or Booking class code
Example: Q |
M |
<SeatItem>
|
A Seat Item with seat characteristic details
This list should be repeated for each passenger and for each flight they purchase the seat for. The details specified in this section must have been taken from SeatAvailabilityRS
Example: If the request is for 2 ADT and 2 flights (LHRAMS and AMSLHR) and both passengers are buying seats in both flights then SeatItem must be repeated 4 times
SeatItem is now optional. Previously, from V0.3, it was mandatory.
|
O |
refs attr
|
Reference to a passenger and flight on which the seat reservation is requested.
Example: T4 F1
|
M |
<Price>
|
Seat price
|
M |
<Total>
|
|
M |
<SimpleCurrencyPrice>
|
Total price for the seat.
Example: 15.00
|
M |
<Descriptions>
|
This is the Seat Description.
|
M |
<Description>
|
|
M |
<Text>
|
The seat category this seat belongs to
Example: GeneralSideSeat
|
M |
<Location>
|
Seat location details
|
M |
<Column>
|
Seat column.
Example: A
|
M |
<Row>
|
Seat row number and row characteristics |
M |
<Number>
|
Seat row number.
Example: 2
|
M |
<BaggageItem>
|
A bag item with bag quantity, passenger & flight details.
|
O
|
refs attr
|
Reference to a passenger and flight(s) on which the additional bag is requested.
Example: T4 F1
|
M
|
<Price>
|
Bag(s) Price
|
M
|
<Total>
|
|
M
|
<SimpleCurrencyPrice>
|
Total price for the bag(s)
Example: 15.00
|
M
|
<BagDetails>
|
Bag details should be passed here
|
M
|
<BagDetail>
|
|
M
|
<ValidatingCarrier>
|
Should always by ‘BA’
|
M
|
<CheckedBags>
|
|
M
|
<CheckedBag>
|
|
M
|
<PieceAllowance>
|
|
M
|
<ApplicableParty>
|
Should Always be ‘Party’
|
M
|
<TotalQuantity>
|
Number of bags
|
M
|
<PieceMeasurements>
|
|
M
|
Quantity attr
|
Number of bags
|
M
|
