Google Flights Scraper & Price Tracker API - Fare Alerts avatar

Google Flights Scraper & Price Tracker API - Fare Alerts

Pricing

from $0.70 / 1,000 results

Go to Apify Store
Google Flights Scraper & Price Tracker API - Fare Alerts

Google Flights Scraper & Price Tracker API - Fare Alerts

Google Flights scraper and price tracker: fares, cheapest day to fly, stops, airlines, CO2 and price history for any route and dates. Google Flights price drop alerts in Slack, Discord, Teams or Telegram. Google Flights API and MCP server for AI agents. Residential proxy included, no login.

Pricing

from $0.70 / 1,000 results

Rating

0.0

(0)

Developer

Akhil rajesh

Akhil rajesh

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 hours ago

Last modified

Features

Limited permissions

Share

Google Flights Scraper & Price Tracker API

Google Flights Scraper & Price Tracker is an Apify Actor that works as a Google Flights API, a fare-drop alert tool and an MCP server for AI agents. Scrape Google Flights fares for any route and date without a login or API key: every itinerary Google lists with its price, airlines, flight numbers, times, stops, layovers, duration and emissions, plus each search's cheapest fare, Google's price level (low, typical or high), its typical price range and about 60 days of price history. Search a range of dates in one run to find the cheapest day to fly.

It is also a flight price tracker. Schedule it with Only changes and each run returns only what moved since the last one: price drops, fares under your target price, price rises and new flights, posted to Slack, Discord, Microsoft Teams or Telegram if you like. It runs as a live API and MCP server for AI agents too.

Why this scraper

  • It tracks fares, not just today's prices. Each route and date keeps its own history: a run reports a drop once, against the price it last reported, and a slow slide is reported once it adds up to your minimum change (1% unless you set it).
  • Target prices that don't nag. Set a target and a fare at or under it is reported once, then again only after it has gone back above the target and come down again.
  • Routes as you'd type them. "Toronto to London", "YYZ-LHR", "NYC to Tokyo", or a Google Flights link. Dates as 2026-12-10, ranges (2026-12-10 to 2026-12-14) or relative (in 30 days, in 2 weeks), so a schedule always searches ahead.
  • Residential proxy included. Google Flights withholds flight data from cloud servers' addresses about half the time. The Actor reads it through its own residential proxy, one address for the whole run, and its cost is in the search price: there's no proxy in your bill and nothing to set up.
  • Clear about what it didn't read. A search Google didn't answer is named in the status message, a place Google Flights doesn't know gets a free row with Google's suggestions, and a run that read nothing fails without charging.
  • Works with other Google Flights Actors' inputs. The input forms of four popular Google Flights scrapers are read as they are (origin and destination fields, departure_id / arrival_id, a searches list, departDaysAhead), so you can switch with the same JSON.

Use cases

  • Fare alerts: a schedule every few hours for your trip that posts to Slack, Discord or Telegram when the fare drops or falls under your target.
  • The cheapest day to fly: a route over a range of dates (2026-12-10 to 2026-12-20), one way or with a 7-day trip; each date's search row has its cheapest fare.
  • Travel and deal sites: fares, price levels and Google's typical range for many routes, refreshed daily.
  • Airline and route research: which airlines fly a route, nonstop or not, how long it takes and what it costs across dates.
  • Corporate travel: watch the routes your team flies and get told when fares are low.
  • AI agents: ask an assistant "what's the cheapest nonstop from Toronto to London in December?" through the MCP server.

How to use it in 4 steps

  1. Type one or more Routes ("New York to London") and Departure dates ("in 30 days", or a date or a range).
  2. For a round trip, set a Return date or a Trip length. Pick passengers, cabin, stops and airlines if you like.
  3. Set Flights per search and Sort flights by if you like.
  4. Run it. For a tracker, tick Only changes, add a target price or an alert webhook, and schedule it.

What you get

Each search gives one search row and its flight rows. Views split them into Overview, Flights and Changes tables.

A search row (one route on one departure date):

{
"type": "search",
"route": "YYZ to London, United Kingdom",
"departureDate": "2026-12-10",
"tripType": "oneWay",
"maxStops": "nonstop",
"currency": "USD",
"flightsFound": 7,
"cheapestPrice": 331,
"cheapestFlight": {"flightNumbers": ["TS 122"], "airlines": ["Air Transat"], "departs": "2026-12-10T21:35",
"arrives": "2026-12-11T09:45", "stops": 0, "durationMinutes": 430},
"cheapestNonstopPrice": 331,
"shortestDurationMinutes": 425,
"priceLevel": "low",
"typicalPrice": 484,
"typicalPriceLow": 335,
"typicalPriceHigh": 890,
"priceHistory": [{"date": "2026-09-11", "price": 341}, "..."],
"airlinesOffered": [{"code": "A3", "name": "Aegean"}, {"code": "EI", "name": "Aer Lingus"}, "..."],
"googleFlightsUrl": "https://www.google.com/travel/flights?q=Flights+to+London%2C+United+Kingdom+from+YYZ+on+2026-12-10+one+way+nonstop&curr=USD&hl=en&gl=US"
}

A flight row (one itinerary): rank, price (for all passengers), pricePerAdult, airlines, flightNumbers, from, to, departs, arrives, arrivesNextDay, durationMinutes, stops, layovers (airport, length, overnight, change of airport), legs (each flight with its airports, times, aircraft, legroom and the airline that operates it), alsoSoldAs (codeshares), emissionsGrams, emissionsVsTypicalPercent and isBest (among Google's best flights). The first row of that search: TS 122 from YYZ to LGW, $331, an Airbus A321neo with 31 inches of legroom, also sold as Porter Airlines.

With Only changes, each reported row also has change (priceDrop, priceRise, belowTarget, newFlight, or firstRun on a tracker's first run), previousPrice, priceChange, priceChangePercent, lowestPriceSeen and isLowestPriceSeen.

A notFound row (free) names a place Google Flights doesn't know, with what its place lookup offered instead.

How to use it

Routes and dates

  • Routes: one per line, as "From to To". Each end can be a city ("London" means all its airports) or an airport code. Up to 50 routes and 100 searches a run.
  • Departure dates: dates (2026-12-10), ranges (2026-12-10 to 2026-12-14, up to 31 days) or relative dates (in 30 days, in 2 weeks, in 3 months, tomorrow). Each route is searched on each date. Google Flights lists flights about 330 days ahead; earlier or later dates are skipped and named.
  • Return date or Trip length (days): a round trip. A trip length works with every departure date.
  • Google Flights links: paste a search link from Google Flights; its route, dates, currency and country are used.

Passengers, cabin and filters

Adults and children; economy, business or first; any number of stops, nonstop only, 1 stop or fewer, or 2 stops or fewer; airlines to keep (codes such as DL) or to leave out. Filters for a maximum price, duration, layover, and departure or arrival times apply to the flight rows and to each search's cheapest fare; flightsMatchingFilters says how many passed.

Output

Flights per search (20 unless you set it, up to 300: Google lists up to about 300) and Sort flights by (price, Google's best order, duration, departure, arrival or emissions). Max results (1,000 unless you set it) caps the run's rows and is shared fairly between searches.

Paused for now

Since November 16, 2026, Google Flights asks every request to its data call for a browser check, which this Actor doesn't pass. The Actor reads each search from the page a visitor opens instead, so a few options are paused until that changes: the price calendar, infants, premium economy, alliances, several places on one side and a country as a destination. A run that asks for infants, premium economy or an alliance is refused before any search, so it costs nothing; one that asks for the others says so and searches the rest, and nothing is charged for what wasn't searched. "1 stop or fewer", "2 stops or fewer" and airline codes still work: the page is searched with every flight, and the ones that don't match are left out (the status says so). The Actor checks every week whether the data call answers again.

Market

Currency (USD unless you set it), Country (the market Google prices for) and Language.

Tracking fares on a schedule (Google Flights price tracker)

Tick Only changes and schedule the Actor (every few hours, or daily). The first run saves each search's fare as the baseline and returns it marked firstRun; later runs return only changes:

  • priceDrop and priceRise: a move of at least Minimum price change (%) (1 by default) since the price last reported; smaller moves don't move the baseline, so a slow slide is reported once it adds up.
  • belowTarget: a fare at or under your Target price, once, until it goes back above it.
  • newFlight: an itinerary Google hadn't listed for this search before.

Pick which ones to report in Changes to report (price drops and fares under your target unless you set it). Track fixed dates (2026-12-10, or a range): a relative date such as "in 30 days" is a new departure day every day, so each day's run is that date's first run. Each search keeps its own history in a named store (google-flights-history, or the History name you give), so several schedules can share it without overwriting each other. Rows are charged only when they are returned, so a tracker that finds nothing new costs only its searches.

Alerts in Slack, Discord, Microsoft Teams or Telegram

Paste an incoming-webhook URL in Alert webhook URL (Slack, Discord, Microsoft Teams, or any HTTPS endpoint that takes JSON, such as Zapier, Make or n8n), or a Telegram bot token and chat id. Either switches on Only changes. The first run posts one short "alerts are set up" message; each later run posts its changes, up to 50 a run, most important first, each with the fare, the move, the flight and a Google Flights link. The URL and the token are treated as secrets and masked in logs. If posting fails, the run still succeeds and its status says why.

Run summary for pipelines

Each run saves a RUN_SUMMARY record in its key-value store: rows by type, the changes, the run's cheapest fare, what wasn't found or didn't load and why, the searches with no flights, and the notes on your input.

Google Flights API: use it from code or from an AI assistant

Run the Actor through Apify's API and read the dataset, as with any Actor:

curl -X POST "https://api.apify.com/v2/acts/akhil_rajesh~google-flights-scraper/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"routes": ["Toronto to London"], "departureDates": ["in 30 days"], "maxFlightsPerSearch": 5}'

For AI agents: MCP server and live API

The same code runs as a live endpoint that answers in seconds, with no run to wait for: Google Flights MCP Server & API, at the same prices.

  • MCP server at https://akhil-rajesh--google-flights-mcp-server.apify.actor/mcp (send your Apify token as Authorization: Bearer <token>), with 3 tools: search_flights (a route on one or more dates, with every filter), find_airport (what a city or airport name means to Google Flights; free) and run_actor (the whole input above).
  • HTTP API at the same host: GET /flights?from=YYZ&to=London&dates=2026-12-10, GET /airports?q=london (free) and POST /run with this Actor's input. GET / lists every parameter.

A request reads up to 10 searches (3 per MCP tool call) and returns the rest as notRead, to send in another request. Tracking and alerts need a scheduled run. Agents that pay per call (x402, Skyfire) can run this Actor through https://mcp.apify.com instead, as a normal run per call.

How much does it cost?

You pay $6.00 per 1,000 searches and $1.00 per 1,000 results, plus a start fee of $0.00005 per run. A search is one route on one departure date, charged once when Google Flights' page for it is read, whatever it lists: each one is a page load through the residential proxy. A result is a flight row or a search row with flights; notFound rows are free, and a search that didn't load isn't charged. Platform usage and the residential proxy are included in runs of the Actor. The live endpoint (Google Flights MCP Server) charges at the same prices, plus the Standby run's platform usage while it serves you.

Apify planPer 1,000 searchesPer 1,000 results
Free$6.00$1.00
Starter$6.00$0.90
Scale$6.00$0.80
Business and above$6.00$0.70
RunSearchesResultsCost (Free plan)
One route on one date, 20 flights121about $0.03
5 routes on 7 dates, 10 flights each35385about $0.60
One route over 30 dates, 5 flights each (the cheapest day)30180about $0.36
A tracker of 3 routes twice a day, a few changes a run6 a dayabout 10 a dayabout $0.05 a day

To cap spending, lower Flights per search or Max results, or set a maximum cost per run in the run options; the Actor stops cleanly at the limit.

Good to know

  • Prices are Google Flights' prices for the market, currency and passengers asked for, as a visitor sees them; they can change between a run and a booking.
  • Booking options (which sellers offer a fare, and their links) aren't read: Google's robots rules close those pages to crawlers. Each row links its Google Flights search, where the booking options are one click away.
  • Multi-city trips, Explore (anywhere) and bag fees aren't covered. A rival input asking for them is searched without them, and the status says so.
  • A place Google Flights doesn't know isn't guessed: it gets a free notFound row with Google's suggestions.
  • Each search is read from its own Google Flights page, the one a visitor opens, after checking that the page read the same search in the currency asked for. The options that page can't say are paused or applied to the rows (see Paused for now); a search that can't be read is named in the status and isn't charged. The run summary counts the searches read and charged (searchesReadFromPage, chargedSearches).
  • The Actor asks Google about once every 3 seconds. After a burst of searches Google can refuse a server's address for several minutes (its "unusual traffic" page). A run then waits, asking again once a minute for up to 10 minutes, and says so in its status; it keeps the same address. The live API and MCP server answer at once instead, naming what Google refused.

FAQ

Is there a Google Flights API? Google has no public Google Flights API: its QPX Express API for airfares closed in 2018. This Actor works as one. Call it through Apify's REST API (run-sync-get-dataset-items returns the flights as JSON), or through the live HTTP endpoint of its MCP server listing (GET /flights?from=JFK&to=LAX&dates=2026-12-10), from any language.

Is there a Google Flights MCP server? Yes: Google Flights MCP Server, at https://akhil-rajesh--google-flights-mcp-server.apify.actor/mcp, with the tools search_flights, find_airport and run_actor. Add it to Claude, Cursor or any MCP client with your Apify token as a Bearer header, then ask for fares in plain language.

How do I get Google Flights price drop alerts? Schedule the Actor with Only changes on, and add a Slack, Discord or Teams webhook or a Telegram bot. Each run then posts only price drops, fares under your Target price, and (if you ask) rises and new flights.

How do I find the cheapest day to fly? Give a route a range of departure dates (2026-12-10 to 2026-12-20) and sort by price: each date's search row has its cheapest fare, and the status names the run's cheapest.

How much does it cost to scrape Google Flights? $6.00 per 1,000 searches plus $1.00 per 1,000 results, with the residential proxy and platform usage included. One route on one date with 20 flights costs about $0.03.

Can I scrape Google Flights with Python? Yes, with the apify-client package: ApifyClient(token).actor("akhil_rajesh/google-flights-scraper").call(run_input={"routes": ["Toronto to London"], "departureDates": ["in 30 days"]}), then read the run's dataset.

Does it show Google Flights price history? Each search row has Google's price level, its typical price range and about 60 days of the route's price history as Google shows it. With Only changes, the Actor also keeps its own history of the fares it reported, with the lowest price seen.

Is it legal to scrape Google Flights? The Actor reads the public fares a visitor sees, at a modest pace, and leaves out the pages Google's robots rules close. Check the laws and terms that apply to how you use the data.

Do I need a proxy? No. The Actor uses its own residential proxy, included in the price. Your own proxy URLs are used instead if you give them; an Apify Proxy setting isn't, since the Actor's own proxy is the one it was tested through.

Why does my run show fewer flights than Google Flights? Flights per search is 20 unless you set it; Google lists up to about 300. Filters and Max results also cut what's returned.

How do I get round-trip prices? Set a Return date or a Trip length. A round trip's price is for the whole trip, as Google shows it for the outbound flights.

Can it watch one exact flight? Yes: track the search with Changes to report set to price drops, and narrow it with Airlines, departure times or Stops; the search row's cheapest fare then follows the flights you care about.

Other Actors by this developer

Disclaimer

This Actor is an independent tool. It is not affiliated with, endorsed by or sponsored by Google. It reads publicly available fares at a modest pace. Use the data in line with Google's terms and the laws that apply to you.