The core of any shopping request is the Origin and Destination, with the dates for each leg of the journey, together with the number of different passenger types travelling.
We remind you that you can use any IATA 3 letter code that can represent a City, Metropolitan Area or a specific Airport/Station.
New or modified element | To be removed/deprecated | Unique to v2 - Branded Fares | Unique to V1 - Fare Families |
NAME | DESCRIPTION | FORMAT | ALLOWED/POSSIBLE VALUES |
|---|---|---|---|
<CoreQuery / OriginDestinations / OriginDestination> (see footnote *) | |||
Attribute OriginDestination@OriginDestinationKey | ID for the Origin/Destination | Alphanumeric | This attribute can be filled with any value, but first character cannot be a number digit or a special character. |
Departure / AirportCode | IATA 3 character code for the departure city/airport/station | 3 Alphanumeric | Any valid departure point listed in the AirlineProfile. |
Departure / Date | Date of departure | Date (yyyy-MM-dd) | Any future date |
Arrival / AirportCode | IATA 3 character code for the arrival city/airport/station | 3 Alphanumeric | Any valid arrival point listed in the AirlineProfile. |
*Round trip on same day - The order of the OriginDestinations will be inferred from the order they are recieved in the AirShoppingRQ when the dates are the same.
