<OrderChangeRQ>
<Document>
<Party>
<Query>
<DataLists>
User Guidance | ||||
Input Parameters | Type | Mandatory/Optional | ||
Request Object | OrderChangeRQ | M | ||
< OrderChangeRQ > | ||||
XML Example for the following elements
| ||||
Elements | Details | Mandatory/Optional | ||
| Specify NDC schema message version. Always pass 17.2 | M | ||
<Document> | ||||
XML Example for the following elements
| ||||
Elements | Details | Mandatory/Optional | ||
| NDC Message Document information | M | ||
| Document name will be always NDC | O | ||
| Will be NDC version | O | ||
<PointOfSale> | ||||
XML Example for the following 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 | ||||
| Applicable for name change , contact addition/modification, travel doc addition/modification | O | ||
Example of Name change
| ||||
| New name details | M | ||
| Passenger id for which name has to be changed | M | ||
| Pax type eg : ADT | M | ||
| This is applicable for name change | M | ||
| Gender for new pax name | M | ||
| NameTitle of new pax name | M | ||
| GivenName of new pax name | M | ||
| Surname of new pax name | M | ||
| Add for new name addition | M | ||
| . 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 | ||
| Old details in case of name change, contact modification or travel doc modification | O | ||
| PassengerID | M | ||
| Pax type eg : ADT | M | ||
| This will come in case of name change | O | ||
| Gender | M | ||
| NameTitle | M | ||
| GivenName of old pax name in case of name change | M | ||
| Surname of old pax name in case of name change | M | ||
| Delete for old name deletion, contact deletion/travel doc deletion | M | ||
| Applicable for segment addition/modifications ,SSR addition/modification , seat addition/modifications | O | ||
| Offer accepted | 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. 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 | ||
| 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 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 | ||
| 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 | ||
| 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 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 | ||
| Price details | M | ||
| Reference 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 OrderReshopForReprice response | 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_AUG.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 will have the order items to be deleted | O | ||
| OrderItemID to be deleted | M | ||
| Payment info | 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 | ||
| ||||
| Defines fare type and fare level | M | ||
| Currency details | M | ||
DataLists | ||||
| Passenger details | M | ||
| Passenger detail | M | ||
| OrderChangeRQ/DataLists/ContactList/ContactInformation@ContactID to be mentioned here if the contact is Passenger Specific | M | ||
| Contact details | M | ||
| ||||
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 | ||
| Service details | M | ||