There is no public Google Flights API for searching or booking flights: Google closed QPX Express, the developer flight API most people mean, in 2018, and its public flight-related API today returns carbon emissions, not fares. To put flight search and booking inside your own product, you need a flight booking API instead — Tripgic, for example, gives one integration to GDS, NDC and low-cost carrier content, with 800+ airline and LCC connections.
This guide explains what the Google Flights API was, why it closed, what Google offers now, why “Google Flights APIs” sold today are mostly scrapers, and how to choose and use a real flight booking API.
Does Google Have a Flights API in 2026?
No — not for searching or booking flights. Here is what exists and what does not:
| Google product | What it is | Can you pull fares into your app? |
|---|---|---|
| QPX Express | The developer flight-search API | No — closed in 2018 |
| QPX (enterprise) | The original ITA pricing engine, licensed to large travel companies | Only through a direct commercial contract |
| Google Flights | The consumer search site | No — it is a website, not an API |
| Travel Impact Model API | Carbon emission estimates per flight | No fares; emissions only |
| Google Flights partner programme | Airlines and agencies send their fares to Google | No — data flows into Google, not out |
For almost every developer and travel business, the honest answer is: you will not add flight search and booking with a Google API.
What Was the Google Flights API?
ITA Software and QPX
In 2010 Google agreed to buy ITA Software, a flight-search company, for about $700 million. ITA’s best-known products were QPX, a fare search and pricing engine used by airlines and travel sites, and the ITA Matrix, a public fare-search tool.
The deal was reviewed by the US Department of Justice, which was concerned that Google could cut competitors off from ITA’s technology. As a condition of approval, Google had to keep licensing QPX to existing and new customers for five years.
QPX Express
Google later launched QPX Express, a simpler version of QPX for developers. This is what most people mean by “the Google Flights API”. It returned flight schedules, availability and fares for a route and date, with filters for airlines, stops and times. It had a small free daily allowance and a low price per query after that, which made it popular with start-ups and hobby projects.
What QPX Express could not do
Even when it existed, QPX Express was a search and pricing API. It did not issue tickets. A business that wanted to sell flights still needed an airline, a GDS connection or a ticketing agency behind it. That limit is often forgotten in the nostalgia for the old API.
Why Google Closed It in 2018
Google gave customers notice in 2018 and closed QPX Express. Two reasons are usually given:
- The obligation had ended. The five-year licensing condition from the ITA deal had expired.
- Google Flights had become the product. An open API feeding the same fares to competing travel sites worked against Google’s own flight search. Google’s stated reason was low use among partners.
The lesson for travel businesses is broader than Google: a free or cheap public flight API can change or close, and products built on it need a plan. Amadeus pushed developers through a similar change with its self-service APIs — see our Amadeus self-service API alternatives guide.
What Google Offers Now
Google Flights, the consumer site
Excellent for a person comparing fares. It cannot be embedded in your product, and every search sends the traveller — and the sale — to an airline or agency through Google.
The Travel Impact Model API
The Travel Impact Model API returns estimated carbon emissions for flights, the figures shown on Google Flights. It is useful for showing emissions beside fares in your own search. It returns no prices, availability or booking.
The Google Flights partner programme
Google’s flights partner documentation looks like an API, which causes confusion. It works the other way round: airlines and online travel agencies send their fares and links to Google so they appear in Google Flights. It is a sales channel into Google, and it needs a bookable source of fares behind it — which is exactly the thing a flight booking API provides.
Three Kinds of “Google Flights API” Alternatives
Most articles list alternatives without saying they are different products. Choose the kind first.

1. Scraper APIs: data only
Several services sell a “Google Flights API”. They load Google Flights results and return them as JSON. They suit one job: price research and monitoring.
Their limits:
- They cannot book. They read a results page; there is nothing to buy.
- They depend on a page they do not control. A layout change can break them overnight.
- They may conflict with terms of service. Using another company’s results pages as a data source carries legal and commercial risk.
- They show what Google shows. If a carrier is missing from Google Flights, it is missing from the scraper.
2. Single-source booking APIs
An airline’s own NDC API, or a provider connected to one main source, lets you search and book. This is a real step up from scraping. The trade-off is coverage: to sell broadly, you add and maintain each source yourself.
3. Multi-source aggregators
An aggregator connects many sources — GDS content, airline NDC connections and low-cost carriers — and returns them through one integration, one format and one booking flow. Your team builds against one API rather than several.
| Scraper API | Single-source booking API | Aggregator | |
|---|---|---|---|
| Can book | No | Yes | Yes |
| Sources | Google’s displayed results | One | Many |
| Stability | Breaks when the page changes | Stable | Stable |
| Legal footing | Uncertain | Contracted | Contracted |
| Best for | Research | Narrow needs | OTAs and platforms that sell flights |
Which One Does Your Product Need?
| Your goal | What to use |
|---|---|
| Track fares for research or a report | A data or scraping service, accepting its limits |
| Show emissions next to fares | The Travel Impact Model API, plus a fare source |
| Sell flights from one airline | That airline’s API |
| Run an OTA, app or booking engine | A booking API with broad coverage — usually an aggregator |
| Appear in Google Flights as a seller | A booking source first, then Google’s partner programme |
If you are choosing between a raw GDS connection and a modern API, see travel API vs GDS. For a shortlist of providers, see the best travel API guide.
Where Flight Content Comes From
A booking API is only as good as the sources behind it:
| Source | What it carries | Notes |
|---|---|---|
| GDS | Most full-service airlines’ fares and schedules | The traditional channel used by travel agencies; see what a GDS is |
| NDC | Airlines’ own offers, often with bundles and extras | Airline-by-airline; see what NDC is |
| Low-cost carriers | Budget airlines’ fares | Many are not in a GDS at all; see our low-cost carrier API guide |
A search built on one source misses fares from the others. That is why an aggregator that combines all three often returns more options and cheaper prices than any single one.
How a Real Flight Booking API Works
A scraper reads a page. A booking API follows a sequence that ends in a ticket:
- Search — send origin, destination, dates, passengers and cabin.
- Offers — receive fares with flights, baggage and rules.
- Price check — confirm the chosen offer’s price and availability, because fares change.
- Book — send passenger details to create the booking (a PNR or order).
- Pay and ticket — the ticket is issued and the e-ticket number returned.
- Service — changes, cancellations and refunds after the sale.
What a search request looks like
Most modern flight APIs take JSON over HTTPS. A search request carries fields like these (a generic example, not any one provider’s format):
{
"origin": "DAC",
"destination": "DXB",
"departure_date": "2026-12-10",
"return_date": "2026-12-17",
"adults": 2,
"children": 0,
"cabin": "economy"
}
The response lists offers, each with flight segments, times, total price, fare rules and baggage. From Python, JavaScript or any language, this is a standard HTTP request — which is why the question “is there a Python library for the Google Flights API?” matters less than “which booking API will I call?”.
What changes after search
The search is the easy part. A real booking product also needs passenger validation, payment, ticketing, schedule-change handling and refunds. Those steps are where a booking API earns its place, and where a scraper has nothing to offer.
Building a “Google Flights-Style” Search
Teams often want Google Flights’ features in their own product. Each has a cost:
| Feature | What it needs |
|---|---|
| Price calendar | Many searches per route — one per date — or a fare cache |
| Price graph and alerts | Stored fare history and repeated searches over time |
| Flexible dates and nearby airports | More searches per traveller request |
| Fast results | Parallel searches across sources, caching of static data |
| Filters | Clean, consistent data on stops, times, airlines and baggage |
Watch the look-to-book ratio
Suppliers measure how many searches you send for each booking you make — the look-to-book ratio — and set limits. Calendar and graph features multiply searches quickly. Plan caching and search limits with your provider before building them, not after.
Using Flight Data Beyond Search
Once you have a reliable flight booking API, the same data supports more of the business:
- Your own booking flow, so customers buy from you rather than from a site they found through Google.
- Pricing decisions, using live fares rather than old ones.
- Packages, combining flights with hotels and transfers — see our dynamic packaging guide.
- Corporate travel tools, with policy rules applied to live fares.
- Market analysis of routes, prices and availability.
All but the last require booking, not only data.
Questions to Ask a Flight API Provider
| Question | Why it matters |
|---|---|
| Which sources are included — GDS, NDC, low-cost carriers? | Coverage decides whether you can compete on price |
| Is the price confirmed before booking? | Avoids charging customers a price you cannot honour |
| Can you issue tickets, or only search? | A search-only API is not a booking API |
| How are changes, cancellations and refunds handled? | Servicing is most of the support work |
| What are the look-to-book limits? | Affects calendar and alert features |
| Is there a free sandbox? | Lets developers test before signing |
| How is pricing structured? | Per booking, per search or subscription changes your costs |
Adding Emissions to Your Own Flight Search
The one Google flight API that is open — the Travel Impact Model — can still improve your product. A common pattern:
- Search fares through your booking API.
- Look up emissions for each flight in the results through the Travel Impact Model API, using the airline, flight number and date.
- Show both in the results, so travellers and corporate travel managers can compare price and emissions side by side.
- Let users sort or filter by lower emissions where that matters to them.
Corporate buyers increasingly report on travel emissions, so showing them can help in business-travel sales. Keep the label clear: the figures are estimates from a model, not measurements of a specific flight.
Key Terms
| Term | Meaning |
|---|---|
| QPX / QPX Express | ITA’s fare search engine and Google’s former developer version of it |
| Offer | A bookable combination of flights, fare and conditions |
| PNR | Passenger name record — the booking in an airline or GDS system |
| Validation | Re-checking an offer’s price and availability before booking |
| Ticketing | Issuing the e-ticket that lets the passenger fly |
| GDS | Global distribution system, the traditional channel for airline content |
| NDC | IATA’s standard for airlines to sell their own offers through APIs |
| LCC | Low-cost carrier |
| Look-to-book ratio | Searches sent for each booking made |
Flight Data API vs Flight Booking API
The two names are often used as if they meant the same thing. They do not:
| Flight data API | Flight booking API | |
|---|---|---|
| Returns | Schedules, statuses, historic or sampled fares | Live, bookable offers |
| Can create a booking | No | Yes |
| Price accuracy | Indicative | Confirmed at validation |
| Typical users | Analysts, apps showing flight status, research tools | OTAs, booking engines, corporate tools |
| Example need | “Is flight EK585 on time?” | “Sell two seats Dhaka–Dubai on 10 December” |
Flight status and schedule data come from different providers than fares, and many products need both: a booking API to sell, and a status feed to tell travellers about delays. Decide which question your product answers before choosing.
What Selling Flights Needs Besides an API
An API gives you bookable content. Selling flights also needs:
- A way to issue tickets. Airlines issue tickets through accredited agents or through the provider’s own ticketing arrangement. Ask your provider how ticketing works for your business.
- Payment handling, with card data processed by a certified payment provider. See our travel API security guide.
- Clear price display including all mandatory taxes and fees, as consumer rules require in many markets.
- Customer service for changes, cancellations, refunds and schedule changes.
- Terms and conditions that explain fare rules, baggage and your role as the seller.
These are business questions, not code questions, and they take as long to settle as the integration itself. Start them in parallel.
How Flight API Pricing Usually Works
Providers charge in a few common ways:
| Model | How it works | Suits |
|---|---|---|
| Per booking or per ticket | A fee each time a ticket is issued | Most OTAs and agencies |
| Per search | A fee per search or per thousand searches | Data-heavy products |
| Subscription | A monthly fee, sometimes with included volume | Steady volume |
| Mixed | A subscription plus a per-booking fee | Larger platforms |
Per-search pricing punishes calendar and alert features; per-booking pricing rewards them. Model your real search and booking numbers before comparing offers.
From Sandbox to First Ticket: A Typical Path
- Sandbox access. Get test credentials and read the documentation.
- Search. Build the search and results page with test data.
- Price check and booking. Add validation and booking, with test passengers.
- Payment. Connect your payment provider and test failures as well as successes.
- Ticketing and documents. Confirm e-ticket numbers arrive and itineraries are sent.
- Servicing. Test cancellations and changes.
- Go-live checks. Error handling, logs, monitoring and support contacts.
- First real booking, watched end to end, then gradual traffic.
Most of the work in steps 4 to 7 is the same whatever provider you choose. That is why picking a provider with broad coverage first saves rework: adding a second source later means repeating much of the path.
Common Mistakes
- Building on a scraper and discovering, after launch, that nothing can be booked.
- Assuming a free API will last. QPX Express and other public programmes have closed or changed.
- Using one source only and missing low-cost carriers or NDC fares.
- Skipping the price check before payment.
- Building calendar features without a cache, then hitting look-to-book limits.
- Forgetting servicing — the work after the ticket is issued.
How Tripgic Fits
Tripgic is a flight booking API, not a scraper. Through one integration it carries:
- 800+ airline and LCC connections, the figure on Tripgic’s homepage and pricing page.
- GDS content from Amadeus, Sabre and Travelport through the GDS API.
- NDC content from airlines’ own APIs through the NDC API.
- 100+ low-cost carriers through the LCC API.
The flow follows the sequence above: search, validation, booking and ticketing. The API documentation states that prices returned at validation and booking are final and can be shown to customers as they are, and that throughput is set to your expected volume and look-to-book ratio. The same integration also carries hotels, transfers, activities and more, with one JSON envelope for every product.
Testing starts in a free sandbox with the same schema as production. A direct GDS integration usually takes 6–12 months; activation with Tripgic is usually 3–5 business days, per the pricing page.
Final Thoughts
The public Google Flights API has been gone since 2018, and Google’s current flight APIs either return emissions or bring fares into Google rather than out of it. Products sold as a “Google Flights API” are mostly scrapers: useful for research, unusable for selling. The question to ask is not “how do I get Google’s data?” but “which source will let me sell this seat?”
If your product must search and book flights, choose a booking API — ideally one that combines GDS, NDC and low-cost carrier content through one integration. Book a demo with Tripgic and test it in the sandbox first.
Akhirul Islam





