IATA_AirShoppingRQ

Owned by Sreejith S R (Unlicensed)
Last updated: Feb 13, 2020
2 min read

 

User Guidance - Service Input Parameters

Input Parameters

Type

Optional/Mandatory

Request Object

IATA_AirShoppingRQ

M

  • <IATA_AirShoppingRQ>

    • <MessageDoc>

    • <Party>

    • <PayloadAttributes>

    • <POS>

    • <Request>

      • <FlightCriteria>

      • <Paxs>

<IATA_AirShoppingRQ>

XML Example for the following elements

<iata:IATA_AirShoppingRQ>

<PayloadAttributes>

XML Example for the following elements

<iata:PayloadAttributes>

       <iata:VersionNumber>19.2</iata:VersionNumber>

</iata:PayloadAttributes>

Elements

Details

Optional/Mandatory

VersionNumber

Specify NDC schema message version. Always pass 19.2

O

<POS>

XML Example for the following elements

<iata:POS>

   <iata:Country>

      <iata:CountryCode>DE</iata:CountryCode>

   </iata:Country>

</iata:POS>

Elements

Details

Mandatory/Optional

Country

Point of sale location information.

 

CountryCode

Country Code

M

<MessageDoc>

XML Example for the following elements

<iata:MessageDoc>

<iata:Name>NDC</iata:Name>

<iata:RefVersionNumber>19.2</iata:RefVersionNumber>

</iata:MessageDoc>

Elements

Details

Optional/Mandatory

<MessageDoc>

NDC Message Document information

O

<Name>

Document name will be always "NDC"

O

<RefVersionNumber>

It will be NDC version

O

<Party>

XML Example for the following elements

Normal bookings/B2C bookings 

<iata:Party>

   <iata:Recipient>

       <iata:ORA>

           <iata:AirlineDesigCode>V1</iata:AirlineDesigCode>

           <iata:Name>Airline Name</iata:Name>

       </iata:ORA>

   </iata:Recipient>

   <iata:Sender>

       <iata:EnabledSystem>

          <iata:Name>Guest Website</iata:Name>

          <iata:SystemID>Guest EN</iata:SystemID>

       </iata:EnabledSystem>

   </iata:Sender>

 </iata:Party>



B2B login/travel agent login

<iata:Party>

   <iata:Recipient>

       <iata:ORA>

           <iata:AirlineDesigCode>V1</iata:AirlineDesigCode>

           <iata:Name>Airline Name</iata:Name>

       </iata:ORA>

   </iata:Recipient>

   <iata:Sender>

       <iata:TravelAgency>

          <iata:AgencyID>Agency code</iata:AgencyID>

             <iata:TravelAgent>

                      <iata:TravelAgentID>Agent ID</iata:TravelAgentID>

                </iata:TravelAgent>

          </iata:TravelAgency>

       </iata:Sender>

 </iata:Party>

Elements

Details

Optional/Mandatory

<Party>

Party & Sender Definition

M

Sender

Message Sender information.

M

EnabledSystem

Used when its B2C login/ Normal login

M

Name

Name. for eg:Guest Website

O

SystemID

Channel Name

M

TravelAgency

Agent User Sender Details. Used when its B2B login/travel agent login

M

AgencyID

Agency Seller Name

M

TravelAgentID

User ID of the Agent

M

Recipient

Named Message Recipient.

M

ORA

SUPPLIER: ORA (Offer Originating Airline)

Recipient.

M

AirlineDesigCode

Airline ID

M

Name

Airline Name

M

NOTE: Channel Information is mandatory and will be fetched from the information given in the SOAP header.

Header: api_access_key

Value: AirlineCode#Channel 

For e.g. XQ#Guest EN

If there is username and password append that to the Value

Value: AirlineCode#Channel#User#Password

< FlightCriteria >

XML Example for the following elements

<iata:FlightCriteria>

   <iata:OriginDestCriteria>

         <iata:CalendarDateCriteria>

               <iata:DaysAfterNumber>1</iata:DaysAfterNumber>

               <iata:DaysBeforeNumber>1</iata:DaysBeforeNumber>

         </iata:CalendarDateCriteria>

         <iata:DestArrivalCriteria>

               <iata:IATA_LocationCode>AYT</iata:IATA_LocationCode>

         </iata:DestArrivalCriteria>

         <iata:OriginDepCriteria>

               <iata:Date>2019-11-29</iata:Date>

               <iata:IATA_LocationCode>FRA</iata:IATA_LocationCode>

         </iata:OriginDepCriteria>

   </iata:OriginDestCriteria>

</iata:FlightCriteria>

Elements

Details

Optional/Mandatory

FlightCriteria

Start of AirShopping Query

M

<OriginDestCriteria>

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 one for EDI-AMS and one for AMS-EDI

M

<OriginDepCriteria>

Departure airport/city details

M

<IATA_LocationCode>

Accepts both airport code (LHR) and city code (LON)

M

<Date>

Departure date

Example: 2015-08-14

M

<DestArrivalCriteria>

Arrival airport/city details

M

<IATA_LocationCode>

Accepts both airport code (LHR) and city code (LON)

M

<CalendarDateCriteria>

Indicates Calendar search date.

Calendar recommendation will only be returned if the client specifies calendar search dates in the request

O

<DaysAfterNumber>

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

<DaysBeforeNumber>

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

 

< Paxs>

XML Example for the following elements

<iata:Paxs>

   <iata:Pax>

         <iata:PaxID>V1_PAX.1</iata:PaxID>

         <iata:PTC>ADT</iata:PTC>

   </iata:Pax>  

</iata:Paxs>

Elements

Details

Optional/Mandatory

<Paxs>

List of all passengers with Passenger type code (PTC)

Example : ADT, CHD, INF

O

Pax

Holds the attributes of any person, specific to a one booking, from shopping to fulfillment.

M

PaxID

Uniquely identifies a Passenger.

M

PTC

Passenger Type code applying to the Passenger. (e.g. ADT, CHD, INF).

O