OrderCreateRQ - LongSell

Owned by Sreejith S R (Unlicensed)
Last updated: Apr 30, 2020
15 min read

  • <OrderCreateRQ>

  • <Document>

  • <Party>

  • <Query>

  • <Payments>

  • <DataLists>

  • <MetaData>

User Guidance

Input Parameters

Type

Mandatory/Optional

Request Object

OrderCreateRQ

M

< OrderCreateRQ >

XML Example for the following elements

<OrderCreateRQ Version="17.2" xmlns="http://www.iata.org/IATA/EDIST">

Elements

Details

Mandatory/Optional

Version (Attribute)

Specify NDC schema message version. Always pass 17.2
Note: This is a mandatory attribute in NDC schema. The service will not validate what is being passed in this attribute

M

 

<Document>

XML Example for the following elements

<Document>         <Name>NDC</Name>         <ReferenceVersion>17.2</ReferenceVersion> </Document>

Elements

Details

Mandatory/Optional

NDC Message Document information

M

Document name will be always NDC

O

Will be NDC version

O

<Party>

XML Example for the following elements

Normal bookings/B2C bookings

 

 

B2B login/travel agent login

Elements

Details

Mandatory/Optional

<Party>

Party & Sender Definition

M

Sender

Message Sender information.

M

AgentUserSender

Agent User Sender Details

M

Name

Agency Seller Name

M

AgentUserID

User ID of the Agent

M

OtherIDs

Additional Agency (Seller) identification

O

OtherID

Other Identifier

M

Description

Other identification description.

M

Recipient

Named Message Recipient.

M

ORA_Recipient

SUPPLIER: ORA (Offer Originating Airline)

Recipient.

M

AirlineID

Airline ID

M

Name

Airline Name

M

<Query>

Query

Core Service Price query parameters.

 

M

Order

 

M

 

Used for selling by value

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

M

Reference to passengers to whom the order item is specified. The passenger reference should be the same as what was defined in PassengerLists.

 

M

Unique ID

V1_OFFERITEM.1560995778608

M

OfferItem for all passengers of the same type.

M

Flight offer item

M

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.

M

Base amount

M

Currency code

o

OriginDestination 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.

 

M

EG: V1_OD.1560995803083

M

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

Unique flight segment key
Example: V1_SEG.1560995803085

This key will be used to associate seat item on a flight.

O

DEPARTURE DETAILS

M

Departure airport code eg : AYT

M

2019-07-05Z

M

11.00

M

Arrival details

M

Airport code eg:FRA

M

Eg : 2019-07-05Z

M

11.00

M

MarketingCarrier information

M

Carrier code

M

FlightNumber EG 123

M

EQUIPMENT DETAILS

M

Eg :73H

M

EG:800

M

Cabin details

M

Eg :Y

M

Cabin name eg ECONOMY

M

Booking class details

M

Selling class or Booking class code

 

M

 

 

Flight journey duration

M

TotalAmount

TotalAmount

TotalAmount

Price details

M

Refernce to passenger id given in PassengerList

M

 

M

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

M

 

M

 

M

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

Currency code eg GBP

M

Base amount

M

Surcharge details

M

 

M

Total surcharge amount

M

Currency code

O

Tax details

M

Total tax amount

M

Currency code

O

FareBasis details

M

FareBasisCode

M

Eg : V1_FMD.1560995778613 . This is defined inside PriceMetadata

M

Fare basis code eg : YOW

M

Gives fare rules

M

Refers to the segment id eg V1_SEG.1560995803085

M

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

 

O

Seat location details

M

Seat column eg A

M

Seat row

M

Seat row number eg 11

M

SEAT CHARACTERISTICS

M

SEAT CHARACTERISTICS

M

Seat keyword

M

Eg :AISLE , WINDOW

M

Reference to associated segment and passenger

M

Flight to which seat is to be added

M

Passenger to whom seat is to be added

M

 

A bag item with bag quantity, passenger & flight details.

O

Reference to a passenger and flight(s) on which the additional bag is requested.

EG: <ns:BaggageItem refs=V1_SSR_1550472531578 V1_SEG_1550472531521 V1_PAX_1">

M

BagDetails

M

BagDetail

M

CheckedBags

M

CheckedBag

M

 

M

Value to be passed ‘Party’

M

 

M

 

M

Baggage description eg CHECKED BAG BY WEIGHT SPREAD OVER ALLOWANCE

M

 

M

Vaue to be passed ‘Party’

M

No:of bags Eg;3

M

 

O

Value to be passed ‘Party’

M

Bag weight details

M

Bag weight eg:25

M

Unit of measurement eg : Kilogram

M

Payments

 

 

 

 

 

M

Payment info

M

Payment info

M

Card details

M

Car code eg VI for VISA

M

Shoud be encrypted

M

Should be encrypted

M

Should be encrypted

M

Billing address

M

Payment amount . To be taken from Offerprice RS

M

Currency code

 

Card expiry details

M

Should be encrypted

M

DataLists

Passenger details

M

Contact details

M

Service details

M

Metadata

 

Defines fare type and fare level

M

Currency details

M