Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

  • <OrderChangeRQ>

  • <Document>

  • <Party>

  • <Query>

  • <DataLists>

User Guidance

Input Parameters

Type

Mandatory/Optional

Request Object

OrderChangeRQ

M

< OrderChangeRQ >

XML Example for the following elements

<OrderChangeRQ 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

<Document>

NDC Message Document information

M

<Name>

Document name will be always NDC

O

< ReferenceVersion>

Will be NDC version

O

<PointOfSale>

XML Example for the following elements

<ns:PointOfSale>
    <ns:Location>
        <ns:CountryCode>IT</ns:CountryCode>
        <ns:CityCode>ROM</ns:CityCode>
    </ns:Location>
    <ns:RequestTime Zone="CET">2019-01-28T07:01:00</ns:RequestTime>
</ns:PointOfSale>

Elements

Details

Mandatory/Optional

Location

Point of sale location information.

CountryCode

Country Code

M

CityCode

Airport or City Code

M

RequestTime

Point Of Sale Timestamp value

Example: 2017-01-13T13:59:38Z

M

Zone

Point of Sale timezone

Example : UTC, CET

M

<Party>

Elements

Details

Mandatory/Optional

<Party>

Party & Sender Definition. Already detailed in above services

M

Query

Query

Core Service query parameters.

M

OrderID

The OrderID to be modified must be mentioned here.

Example : TBG676

M

Owner

(attribute)

Accepts the Airline Code

Example : V1

M

PassengerServicing

PassengerServicing

Applicable for name change , contact addition/modification, travel doc addition/modification

O

Example of Name change

<ns:PassengerServicing>
    <ns:New PassengerID = "V1_PAX_51093937">
        <ns:PTC>ADT</ns:PTC>
        <ns:Individual>
            <ns:Gender>Male</ns:Gender>
            <ns:NameTitle>MR</ns:NameTitle>
            <ns:GivenName>ABDUL</ns:GivenName>
            <ns:Surname>REHUMAN</ns:Surname>
        </ns:Individual>
        <ns:ActionType
            xsi:type = "xs:string"
            xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
            xmlns:xs = "http://www.w3.org/2001/XMLSchema">Add</ns:ActionType>
    </ns:New>
    <ns:Previous PassengerID = "V1_PAX_51093937">
        <ns:PTC>ADT</ns:PTC>
        <ns:Individual>
            <ns:Birthdate>1993-03-29Z</ns:Birthdate>
            <ns:Gender>Male</ns:Gender>
            <ns:NameTitle>MR</ns:NameTitle>
            <ns:GivenName>DYRM</ns:GivenName>
            <ns:Surname>ALB</ns:Surname>
        </ns:Individual>
        <ns:ActionType
            xsi:type = "xs:string"
            xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
            xmlns:xs = "http://www.w3.org/2001/XMLSchema">Delete</ns:ActionType>
    </ns:Previous>
</ns:PassengerServicing>

New

New name details

M

PassengerID

Passenger id for which name has to be changed

M

PTC

Pax type eg : ADT

M

Individual

This is applicable for name change

M

Gender

Gender for new pax name

M

NameTitle

NameTitle of new pax name

M

GivenName

GivenName of new pax name

M

Surname

Surname of new pax name

M

ActionType

Add for new name addition

M

ContactInfoRef

. This will come in case of passenger specific contact change .The Contact Info Reference which is mentioned in ContacList (OrderChangeRQ/DataLists/ContactList/ContactInformation @ContactID)

M

Previous

Old details in case of name change, contact modification or travel doc modification

O

PassengerID

PassengerID

M

PTC

Pax type eg : ADT

M

Individual

This will come in case of name change

O

Gender

Gender

M

NameTitle

NameTitle

M

GivenName

GivenName of old pax name in case of name change

M

Surname

Surname of old pax name in case of name change

M

ActionType

Delete for old name deletion, contact deletion/travel doc deletion

M

OrderServicing

Applicable for segment addition/modifications ,SSR addition/modification , seat addition/modifications

O

AcceptOffer

Offer accepted

M

<OrderItem>

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

REFS

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

M

OfferItemID

Unique ID. This must be the same as that present in OrderReshopRS#Response#ReshopOffers#ReshopOffer#AddOfferItem#OfferItemID

V1_OFRITM_PAX.2147487627_SEG.500-SEG.501

In case of Seat, it must be taken from SeatAvaliabilityRS# ALaCarteOffer#ALaCarteOfferItem#OfferItemID

V1_OFFERITEM.1579392457996

M

OfferItemType

OfferItem for all passengers of the same type.

M

DetailedFlightItem

Flight offer item

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 OrderReshop For Reprice response. The total fare and total tax are compared against the total fare and total tax returned during the booking process.

M

BaseAmount

Base amount

M

Code

Currency code

o

OriginDestination

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

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: V1_SEG.1560995803085

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

O

Departure

DEPARTURE DETAILS

M

AirportCode

Departure airport code eg : AYT

M

Date

2019-07-05Z

M

Time

11.00

M

Arrival

Arrival details

M

AirportCode

Airport code eg:FRA

M

Date

Eg : 2019-07-05Z

M

Time

11.00

M

MarketingCarrier

MarketingCarrier information

M

AirlineID

Carrier code

M

FlightNumber

FlightNumber EG 123

M

Equipment

EQUIPMENT DETAILS

M

AircraftCode

Eg :73H

M

AirlineEquipCode

EG:800

M

CabinType

Cabin details

M

Code

Eg :Y

M

Name

Cabin name eg ECONOMY

M

ClassOfService

Booking class details

M

Code

Selling class or Booking class code

M

Details

FlightDuration

Flight journey duration

M

FareDetail

Price details

M

PassengerRefs

Reference to passenger id given in PassengerList

M

FareComponent

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

M

TotalAmount

M

DetailCurrencyPrice

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 OrderReshopForReprice response
Example: 373

M

Code

Currency code eg GBP

M

BaseAmount

Base amount

M

Surcharges

Surcharge details

M

Surcharge

M

Total

Total surcharge amount

M

Code

Currency code

O

Taxes

Tax details

M

Total

Total tax amount

M

Code

Currency code

O

FareBasis

FareBasis details

M

FareBasisCode

FareBasisCode

M

Refs

Eg : V1_AUG.1560995778613 . This is defined inside PriceMetadata

M

Code

Fare basis code eg : YOW

M

FareRules

Gives fare rules

M

SegmentRefs

Refers to the segment id eg V1_SEG.1560995803085

M

Delete

This will have the order items to be deleted

O

OrderItemID

OrderItemID to be deleted

M

Payments

Payment info

M

Payment

Payment info

M

Method

Payment info

M

PaymentCard

Card details

M

CardCode

Car code eg VI for VISA

M

CardNumber

Shoud be encrypted

M

SeriesCode

Should be encrypted

M

CardHolderName

Should be encrypted

M

CardHolderBillingAddress

Billing address

M

Amount

Payment amount. To be taken from OfferPrice RS

M

Code

Currency code

EffectiveExpireDate

Card expiry details

M

Expiration

Should be encrypted

M

<ns:OrderChangeMetadata>
    <ns:Other>
        <ns:OtherMetadata>
            <ns:PriceMetadatas>
                <ns:PriceMetadata MetadataKey = "V1_MDK_1548820851567">
                    <ns:AugmentationPoint>
                        <ns:AugPoint Key = "V1_AUG.1556809638256">
                            <ibs:FareDetailAugPoint>
                                <FareType>SUNECO</FareType>
                                <FareLevel>ST</FareLevel>
                                <FareId>327347</FareId>
                            </ibs:FareDetailAugPoint>
                        </ns:AugPoint>
                    </ns:AugmentationPoint>
                </ns:PriceMetadata>
            </ns:PriceMetadatas>
            <ns:CurrencyMetadatas>
                <ns:CurrencyMetadata MetadataKey = "EUR">
                    <ns:Decimals>2</ns:Decimals>
                </ns:CurrencyMetadata>
            </ns:CurrencyMetadatas>
        </ns:OtherMetadata>
    </ns:Other>
</ns:OrderChangeMetadata>
PriceMetadatas

Defines fare type and fare level

M

CurrencyMetadatas

Currency details

M

DataLists

PassengerList

Passenger details

M

Passenger

Passenger detail

M

ContactInfoRef

OrderChangeRQ/DataLists/ContactList/ContactInformation@ContactID to be mentioned here if the contact is Passenger Specific

M

ContactList

Contact details

M

<ns:ContactList>
    <ns:ContactInformation ContactID = "V1_CNTCT.1406146459631">
        <ns:ContactType>PAX_SPECIFIC_CONTACT</ns:ContactType>
        <ns:PostalAddress>
            <ns:Label>AddressAtOrigin</ns:Label>
        </ns:PostalAddress>
        <ns:ContactProvided>
            <ns:EmailAddress>
                <ns:Label>EMAIL_ID</ns:Label>
                <ns:EmailAddressValue>ww@ww.com</ns:EmailAddressValue>
            </ns:EmailAddress>
        </ns:ContactProvided>
        <ns:ContactProvided>
            <ns:Phone>
                <ns:Label>CELL_NUMBER</ns:Label>
                <ns:CountryDialingCode>+33</ns:CountryDialingCode>
                <ns:PhoneNumber>1236547891</ns:PhoneNumber>
            </ns:Phone>
            <ns:Phone>
                <ns:Label>SendItineraryAsSMS</ns:Label>
                <ns:CountryDialingCode>+33</ns:CountryDialingCode>
                <ns:PhoneNumber>1236547891</ns:PhoneNumber>
            </ns:Phone>
        </ns:ContactProvided>
    </ns:ContactInformation>
</ns:ContactList>

ContactInformation

Contact details

M

ContactID

The unique ID

Example : V1_CNTCT.1406332458283

M

ContactType

Contact Type

Example :

Passenger specific contact modification : PASSENGER_SPECIFIC_CONTACT,

PNR Contact Modification : PERSONAL,BUSINESS,AGENCY,HOME,PERSONAL_PRIMARY, BUSINESS_PRIMARY,AGENCY_PRIMARY,HOME_PRIMARY

Emergency Contact Modification : E

M

PostalAddress

Receiver Address

O

Label

Label for identifying the type of details provided in the postal address.

Example : AddressAtOrigin

M

CountryName

Country Name

M

ContactProvided

Contact details

M

EmailAddress

Email details

O

Label

Label for identifying the type of details provided for Email.

Example : EMAIL_ID

M

EmailAddressValue

Email address

Example : ww@ww.com

M

Phone

Phone details

M

Label

Label for identifying the type of details provided for Phone.

Example: CELL_NUMBER.

Provide “SendItineraryAsSMS” in case SMS needs to be provided

M

CountryDialingCode

Country Code

M

PhoneNumber

Phone number

M

ServiceDefinitionList

Service details

M

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.