...
User Guidance - Service Input Parameters | ||
Input Parameters | Type | Optional/Mandatory |
Request Object | AirShoppingRQ | M |
<AirShoppingRQ>
<Document>
<Party>
<CoreQuery>
<DataLists>
<AirShoppingRQ> | |||||||
XML Example for the following elements
| |||||||
Elements | Details | Optional/Mandatory code | |||||
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
| |||||||
Elements | Details | Optional/Mandatory | |||||
Code Block | Document | NDC Message Document information | M | ||||
Code Block | Name | Document name will be always "NDC" | O | ||||
Code Block | ReferenceVersion | It will be NDC version | O | ||||
<PointOfSale> | |||||||
XML Example for the following elements
| |||||||
Code Block | Elements | Details | Mandatory/Optional code | ||||
PointOfSale | Point of Sale information. | M | |||||
Location | Point of sale location information. | code O | |||||
CountryCode | Country Code | M code | |||||
CityCode | Airport or City Code | M code | |||||
RequestTime | Point Of Sale Timestamp value Example: 2017-01-13T13:59:38Z | M | code O | ||||
Zone (Attribute) | Point of Sale timezone Example : UTC, CET | MO |
<Party> | |||||||||||||||||||||||||
XML Example for the following elementsNormal bookings/B2C bookings
B2B login/travel agent login
| |||||||||||||||||||||||||
Elements | Details | Optional/Mandatory | |||||||||||||||||||||||
<Party>Party | Party & Sender Definition | M | |||||||||||||||||||||||
Sender | Message Sender information. | M | |||||||||||||||||||||||
AgentUserSender | Agent User Sender Details | M | |||||||||||||||||||||||
Name | Agency Seller Name | MO | |||||||||||||||||||||||
AgentUserID | User ID of the Agent
Example:
| M | |||||||||||||||||||||||
Owner (Attribute) | Airline designator or CRS code of the owner/ assigner of the Offer ID, typically used for offer ordering purposes.
Example:
| O | |||||||||||||||||||||||
OtherIDs | Additional Agency (Seller) identification
| O | |||||||||||||||||||||||
OtherID | Other Identifier | M | |||||||||||||||||||||||
Description (Attribute) | 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 | MO | |||||||||||||||||||||||
<CoreQuery> | |||||||||||||||||||||||||
XML Example for the following elements
| |||||||||||||||||||||||||
Elements | Details | Optional/Mandatory | |||||||||||||||||||||||
Code Block | CoreQuery | Start of AirShopping Query | M | ||||||||||||||||||||||
code OriginDestinations | |||||||||||||||||||||||||
<OriginDestinations> | Origin and destination (O&D) details | M | |||||||||||||||||||||||
Code Block | OriginDestination | This must be repeated for each O&D. If the request is for EDI-AMS return then this must be repeated twice one for EDI-AMS and one for AMS-EDI | M code | ||||||||||||||||||||||
OriginDestinationKey (attribute) | This is the unique key to be used when requesting any preference at Origin-Destination level | O | |||||||||||||||||||||||
Code Block | Departure | Departure airport/city details | M | ||||||||||||||||||||||
Code Block | AirportCode | Accepts both airport code (LHR) and city code (LON) | M | ||||||||||||||||||||||
Code Block | Date | Departure date Example: 2015-08-14 | M | ||||||||||||||||||||||
|
| Arrival | Arrival airport/city details | M | |||||||||||||||||||||
Code Block | AirportCode | Accepts both airport code (LHR) and city code (LON) | M Code Block | | |||||||||||||||||||||
Date | Arrival date Example: 2016-08-14 | O | |||||||||||||||||||||||
CalendarDates | Indicates Calendar search date. Calendar recommendation will only be returned if the client specifies calendar search dates in the request | O code | |||||||||||||||||||||||
DaysAfter (Attribute) | The number of days after the requested date Example: 3 Calendar recommendation will be returned for the number of days specified after the requested date | O code | |||||||||||||||||||||||
DaysBefore (Attribute) | The number of days before the requested date Example: 3 Calendar recommendation will be returned for the number of days specified before the requested date | O |
<Preference> | ||||||||||||
Elements | Details | Optional/Mandatory | ||||||||||
code Preference | ||||||||||||
<Preference> | Fare and cabin preference can be specified here | O | ||||||||||
FarePreferences | Specify fare preference. | O | ||||||||||
XML Example for the following elements
| ||||||||||||
<FarePreferences> | Specify fare preference. | O |
| |||||||||
CabinPreferences | Specify Cabin preference code. | O | ||||||||||
XML Example for the following elements
| ||||||||||||
<DataLists> | ||||||||||||
XML | Elements | Details | Optional/Mandatory | |||||||||
|
| List of all passengers with Passenger type code (PTC) | PassengerList | Passenger data list definition/details. | M | |||||||
XML Example for the following elements
| ||||||||||||
| Passenger | Any person except members of the crew carried or to be carried with the consent of the carrier, on board of any transport vehicle such as aircraft, train, bus, ship.
| M | |||||||||
| PassengerID (Attribute)
| Uniquely identifies a Passenger within the context of one message. Example: V1_PAX.1, V1_PAX.2 ,V1_PAX.3 | M | |||||||||
| PTC | Type code applying to the Passenger which typically drives pricing. Example: ADT, CHD, INF | OM |