Overview
AirShopping API initiates the shopping flow by retrieving travel solutions based on the traveller’s search criteria (such as origin & destination, travel dates, and passenger details)
Click here to view the AirShopping Technical Specification
Current scope
The AirShopping message is used primarily to search and propose offers on the basis of the itinerary and search criteria provided. The search can be performed for fixed dates or in calendar mode.
The following are considered in the scope of the current Altea NDC release:
- Itineraries for 1 to 9 passengers.
- One-Way Display (OWD) mode, for round trip and open jaws.
- Itinerary (ITI) mode, including for open jaws and complex itineraries up to 4 bounds.
- Airline marketed and operated flights, and interline with partner, depending on airline configuration and preferences.
- Ancillary Services - depending on Airline setup (see Pre-requisites section below).
- Calendar mode for search for a range of dates. In this case, a subsequent AirShopping request on chosen date will be necessary for the creation of an Offer.
- Localised fare conditions from static file.
Out of scope
- One Way Combinable (OWC) mode.
- Group - the ability to request availability for more than 9 passengers.
- Ancillary services are not supported in One Way Display or Calendar mode. Pre-requisites
- The required fare families must be filed in the Amadeus database via FareXpert or synchronized from ATPCo fillings.
- The AirShopping request is received with valid XML format (as defined in the IATA XSD).
- For Ancillary Services: the required Ancillary services must be filed in the Amadeus database via FareXpert or synchronized from ATPCo filings. The prices for Ancillary Services filed in ATPCo need to align with the client's Fare Families.