Search ITA Matrix for itineraries. A trip is a list of legs (slices): • 1 slice = one-way • 2 slices = round-trip (second slice reverses the first) • 3+ = multi-city / open-jaw — legs need not connect Each leg takes its own routing code, so you can pin a carrier, force a connection city, or require a specific number of flights per leg. Expect 20-60s. Returns ranked itineraries and a Search ID for get_itinerary_details.

Show per-segment detail for one itinerary from a previous search: operating flight numbers, booking class (RBD), fare basis codes, and aircraft type. Reuses the earlier search session, so it is fast.

Scan a range of departure dates and report the cheapest fare on each, to find when to fly. Runs one search per date, so keep ranges modest (a 14-day scan takes several minutes). For a single date with ±flexibility, use search_flights with flexDays instead.

Resolve a partial city or airport name to IATA codes. Use this when the user names a place rather than a code, or to find the metro code that covers every airport in a city.

Full syntax for the routing and extraCodes fields: carrier pinning, forced connection points, alliances, exclusions, stop counts, and fare-bucket filters. Read this before composing a non-trivial routing code.