Expedia Flights API

Expedia Group has Rapid APIs and partner products, but Rapid access starts with becoming an Expedia Group partner. Public Rapid material is mostly lodging-first, and you should not assume there is an instant public Expedia flights API that arbitrary developers can use without a partner path or contract.

If your goal is specifically to search flight fares and hand users off to booking pages, Ignav is narrower and easier to start with. It does not give you Expedia inventory or a full Expedia booking stack.

What developers are usually trying to build

Expedia API searches usually come from teams building a travel portal, loyalty product, package flow, internal travel tool, or comparison page. For flights, the practical need is often smaller than that: show current route prices, filter itineraries, and send the traveler to a place where the fare can be booked.

Using Ignav for the flight piece

Ignav covers the fare-search and booking-link portion with four endpoints: one-way fares, round-trip fares, booking links, and airport search. Fare results include prices, carriers, segments, baggage fields, and an ignav_id. Booking-link lookups return airline and OTA URLs for the chosen itinerary.

Access is self-serve after email verification. You get 1,000 free requests, then pay $2.00 per 1,000 successful requests. Failed requests are not billed, and authenticated API use has no per-account rate limit.

What Ignav does not cover

Ignav does not replace Expedia Rapid, lodging APIs, package booking, payments, post-booking service, or Expedia partner economics. It also does not sell flights, issue tickets, manage orders, or handle traveler changes. Use it when link-out is enough.