Google Flights API
No public API. Google shut down QPX Express, its only self-serve airfare API, in April 2018; QPX Enterprise (ITA) survives as a bespoke enterprise contract with no public docs or pricing. The vacuum is filled by scraper vendors working against the consumer UI.
Frequently asked questions
Google Flights scores F on the API Report Card. No public API. Google shut down QPX Express, its only self-serve airfare API, in April 2018; QPX Enterprise (ITA) survives as a bespoke enterprise contract with no public docs or pricing. The vacuum is filled by scraper vendors working against the consumer UI.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Google Flights is Google LLC's consumer-facing flight metasearch product, launched in September 2011 as Flight Search following Google's $700M acquisition of ITA Software (Cambridge, Massachusetts) in July 2010 (DOJ-approved April 2011).
Vertical: Travel & Expense (specifically: flight metasearch + airfare shopping/pricing infrastructure). The B2C target market is global leisure and business travelers comparing flight options before booking direct with an airline or OTA. Consumers searching for flights via google.com/travel/flights, Google Search inline flight results, Google Maps trip planning, or the Google app on iOS/Android.
Very high on the consumer side, near-zero on the developer/API side.
Itinerary search inputs: origin/destination airports, dates, passenger counts, cabin class, filters (stops, airlines, alliances, layover length, duration, baggage). Search session and user-account history (signed-in Google account ties searches to Google profile).
Underlying QPX technology is 35+ years old (ITA Software founded 1996, QPX developed in the late 1990s). The Google Flights consumer product launched September 13, 2011 (15 years old as of 2026).
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.