Google Flights API. What happened to the Google Flights API, why it was discontinued, and the best Google Flights API alternatives for developers. Compare flight data APIs, get real-time flight status, schedules and pricing data.
Google Flights API. What happened to the Google Flights API, why Google discontinued its QPX Express API, and which flight data APIs developers should use instead. Google Flights API alternatives, free flight API options and real-time aviation data for your applications.
The Google Flights API, officially known as the QPX Express API, was a flight search and pricing API that Google offered to developers through the Google Cloud Platform. Launched as part of Google's acquisition of ITA Software in 2011 for $700 million, the QPX Express API allowed developers to search for flight itineraries, retrieve fare information and access airline pricing data programmatically.
The QPX Express API provided access to the same flight search engine that powers Google Flights — the consumer-facing flight comparison tool at google.com/flights. Developers could send search queries specifying origin, destination, travel dates and passenger counts, and receive back a structured response with available itineraries, fare breakdowns and carrier information.
However, Google discontinued the QPX Express API on April 10, 2018. The official announcement stated that the API was being shut down and would no longer be available to developers. Google did not provide a direct replacement, leaving thousands of travel applications, startups and booking platforms scrambling to find alternative flight data sources.
"Google's QPX Express API was shut down in April 2018 with no direct replacement. Developers who relied on it had to find alternative flight data sources. Today, modern aviation data APIs offer broader coverage — including real-time tracking, live schedules, fleet data and airport information — capabilities that QPX Express never provided."
Google never publicly disclosed the exact reasons for shutting down the QPX Express API, but several factors likely contributed to the decision:
Before its shutdown, the QPX Express API provided the following capabilities:
| Feature | QPX Express API | Available Today via AirLabs |
| Flight search by route | ✅ Origin/destination search | ✅ Routes Database |
| Airline information | ✅ Basic carrier data | ✅ Airlines Database — 15,000+ carriers |
| Airport codes and data | ✅ IATA codes only | ✅ Airports Database — 9,000+ airports with geo, timezone, connections |
| Flight schedules | ❌ Not available | ✅ Schedules API — live departures/arrivals with gates, terminals, delays |
| Real-time flight tracking | ❌ Not available | ✅ Real-Time Flights API — live lat/lng, altitude, speed, heading |
| Flight status and delays | ❌ Not available | ✅ Flight Info API — status, delays, gates, terminals for any flight |
| Aircraft fleet data | ❌ Not available | ✅ Fleets Database — aircraft type, age, registration, manufacturer |
| Nearby airport search | ❌ Not available | ✅ NearBy API — find airports by coordinates and radius |
| Flight alerts | ❌ Not available | ✅ Flight Alert API — push notifications on status changes |
| Fare pricing | ✅ Itinerary pricing | ❌ Not available (see note below) |
As the comparison shows, while QPX Express provided fare pricing data that AirLabs does not, AirLabs offers an entire suite of aviation data capabilities that QPX Express never had — real-time tracking, live schedules, fleet databases, airport geolocation and flight alerts. For the vast majority of travel application use cases, the data available through AirLabs is more comprehensive than what QPX Express provided.
Since the shutdown of QPX Express in 2018, the flight data API landscape has evolved significantly. Developers today have several categories of alternatives to choose from, each serving different use cases:
These APIs provide operational flight data — real-time positions, departure/arrival schedules, delays, airline information and airport data. They are the best choice for applications that need to display flight information, build tracking tools, show airport timetables or integrate aviation data into business workflows.
AirLabs is an aviation data API. Our platform provides:
Here is an example of the real-time data available through the AirLabs Flights API:
https://airlabs.co/api/v9/flights?airline_iata=AA&api_key={API_KEY}
[{
"hex": "A12345",
"reg_number": "N787AL",
"flag": "US",
"lat": 40.6413,
"lng": -73.7781,
"alt": 10972,
"dir": 225,
"speed": 870,
"flight_iata": "AA100",
"flight_icao": "AAL100",
"dep_iata": "JFK",
"dep_icao": "KJFK",
"arr_iata": "LHR",
"arr_icao": "EGLL",
"airline_iata": "AA",
"airline_icao": "AAL",
"aircraft_icao": "B789",
"status": "en-route"
}]
If your primary need is fare search and ticket booking — the specific functionality that QPX Express provided — you need a booking API rather than a data API. Booking APIs connect to GDS systems and provide real-time fare search, seat availability and reservation capabilities. AirLabs does not provide fare pricing or booking functionality — our focus is operational flight data. If you need fares, you can pair AirLabs (for flight tracking, schedules and airport data) with a separate booking API (for pricing and reservations) to get complete coverage for your travel application.
Some developers attempt to scrape Google Flights directly using headless browsers or third-party scraping services. While technically possible, this approach has significant drawbacks: it violates Google's Terms of Service, is unreliable due to frequent UI changes, is slow compared to proper APIs, cannot provide real-time tracking data, and can result in IP bans. A structured flight data API is always a more reliable and maintainable choice for production applications.
AirLabs is designed specifically for developers who need reliable, structured aviation data. Here is why developers choose AirLabs after the Google Flights API shutdown:
If you previously used the QPX Express API and need to migrate, the transition is straightforward. While AirLabs does not replicate QPX Express fare search, it covers the operational data layer that many QPX Express users actually needed:
| QPX Express Use Case | AirLabs Equivalent | Endpoint |
| "Show flights from JFK to LAX" | Query routes between airports | Routes API |
| "What airlines fly this route?" | Get operating carriers | Routes API + Airlines DB |
| "Is flight AA100 on time?" | Get real-time flight status | Flight Info API |
| "Show me today's departures from JFK" | Live departure schedule | Schedules API |
| "Where is my flight right now?" | Real-time aircraft position | Flights API |
| "Alert me when flight status changes" | Push notification on change | Alert API |
| "Find airports near this location" | Geographic airport search | NearBy API |
| "What type of aircraft is on this route?" | Fleet and aircraft data | Fleets DB |
The AirLabs API uses the same RESTful pattern as QPX Express — HTTP GET requests with query parameters, JSON responses, API key authentication. Developers familiar with the QPX Express request/response format will find the transition intuitive.
If you are a developer looking for a Google Flights API alternative, AirLabs provides the aviation data infrastructure you need. Whether you are building a flight tracking application, an airport information display, a travel planning tool or an airline analytics platform, our API delivers the data in a format that is easy to integrate and reliable to use.
Our Developer API allows you to create a custom experience for your users and increase the value of your product:
You can try it right now without any obligation! Get a free flight API plan and see for yourself that we have exactly the data you need!
If you need more information, don't hesitate to contact us. We are always happy to chat with our customers and are sure to find a customized solution for each request.
Explore AirLabs, or create an account instantly and start using API.
Get FREE API Key