This service is used to request priced availability for flights for the requested origin and destination, date and cabin. The service also returns priced availability for the next higher cabins (normally the next 2 higher cabins). Example, if the availability is requested for Economy, service will return priced availability for Economy, Premium Economy and Business (assuming these cabins are offered on the route requested).

The V1 version which uses the Fare Family concept, and the FareDetail information is limited to certain pricing information. We strongly recommend you migrate to use the V2 version based on Branded Fares.

The V2 version, takes advantage of ATPCo Branded Fares, which includes product attributes filed with the fares. This version of our AirShopping message also includes various improvements in quality of information, such as: Penalty attributes indicating whether there is a penalty charged for either a change, refund or cancel of the booking; and Baggage Allowance information; and cabin information for each flight segment.

The AirShoppingRQ message is made up of the following sections:

Common Sections

HTTP Header

Language, Version and Name Space

Point of Sale

Document

Party

In addition to the Common Sections, this service is called with the following data:

Parameters

CoreQuery

This is the principal part of the AirShoppingRQ, whose main elements are the Origin (Departure) and Destination(Arrival) Cities/Airports and departure date.

Preference

Can, optionally, indicate flight, fare and cabin preferences.

DataLists / PassengerList

This is where you specify the number of passengers and their type

Example AirShoppingRQ:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header/> <soapenv:Body> <AirShoppingRQ Version="5.000" PrimaryLangID="es" xmlns="http://www.iata.org/IATA/EDIST/2017.2"> <PointOfSale> <Location> <CountryCode>ES</CountryCode> </Location> </PointOfSale> <Document> <ReferenceVersion>5.000</ReferenceVersion> </Document> <Party> <Sender> <CorporateSender> <ID>XXXXXXXX</ID> </CorporateSender> </Sender> <Participants> <Participant> <TravelAgencyParticipant SequenceNumber="1"> <Name>NDC Agency Name</Name> <Contacts> <Contact> <EmailContact> <Address>email@email.com</Address> </EmailContact> <PhoneContact> <Application>BUSINESS</Application> <Number>#########</Number> </PhoneContact> <Name> <Surname>Martinez</Surname> <Given>Pepe</Given> </Name> </Contact> </Contacts> <IATA_Number>XXXXXXXX</IATA_Number> <AgencyID>XXXXXXXX</AgencyID> </TravelAgencyParticipant> </Participant> </Participants> </Party> <CoreQuery> <OriginDestinations> <OriginDestination OriginDestinationKey="IDA"> <Departure> <AirportCode>MAD</AirportCode> <Date>2022-04-25</Date> </Departure> <Arrival> <AirportCode>PAR</AirportCode> </Arrival> </OriginDestination> <OriginDestination OriginDestinationKey="VUELTA"> <Departure> <AirportCode>PAR</AirportCode> <Date>2022-04-30</Date> </Departure> <Arrival> <AirportCode>MAD</AirportCode> </Arrival> </OriginDestination> </OriginDestinations> </CoreQuery> <Preference> <FlightPreferences> <Characteristic> <DirectPreferences>0</DirectPreferences> </Characteristic> </FlightPreferences> <PricingMethodPreference> <BestPricingOption>C</BestPricingOption> </PricingMethodPreference> </Preference> <DataLists> <PassengerList> <Passenger PassengerID="Pasajero1"> <PTC>ADT</PTC> </Passenger> <Passenger PassengerID="Pasajero2"> <PTC>ADT</PTC> </Passenger> <Passenger PassengerID="Pasajero3"> <PTC>ADT</PTC> </Passenger> </PassengerList> </DataLists> </AirShoppingRQ> </soapenv:Body> </soapenv:Envelope>

Examples AirShoppingRQ 2024:

<Sender> <CorporateSender> <ID>IXXXXXXS</ID> </CorporateSender> </Sender>