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 traveling.

We remind you that you can use any IATA 3 letter code that can represent a City, Metropolitan Area or a specific Airport/Station.

NAME	DESCRIPTION	FORMAT	ALLOWED/POSSIBLE VALUES
*<CoreQuery / OriginDestinations> (see footnote )**
OriginDestination Attribute 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.
OriginDestination / Departure / AirportCode	IATA 3 character code for the departure city/airport/station	3 Alphanumeric	Any valid departure point listed in the AirlineProfile.
OriginDestination / Departure / Date	Date of departure	Date (yyyy-MM-dd)	Any future date
OriginDestination / 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 received in the AirShoppingRQ when the dates are the same.

CoreQuery AirShoppingRQ example:

<CoreQuery>
	<OriginDestinations>
		<OriginDestination>
			<Departure>
				<AirportCode>MAD</AirportCode>
				<Date>2024-08-19</Date>
			</Departure>
			<Arrival>
				<AirportCode>LIS</AirportCode>
			</Arrival>
		</OriginDestination>
		<OriginDestination>
			<Departure>
				<AirportCode>OPO</AirportCode>
				<Date>2024-09-01</Date>
			</Departure>
			<Arrival>
				<AirportCode>MAD</AirportCode>
			</Arrival>
		</OriginDestination>
	</OriginDestinations>
</CoreQuery>

IB NDC Documentation

Core Query

CoreQuery AirShoppingRQ example: