Google Flights Price Tracker API 💰$0.8/1k
Pricing
from $0.52 / 1,000 results
Google Flights Price Tracker API 💰$0.8/1k
💰$0.8/1k — Track Google Flights fares over time. Watch routes and get price-drop alerts via Telegram, Slack, Discord or WhatsApp. Incremental runs return only NEW/UPDATED itineraries with the delta vs the last run. JSON/CSV. API + MCP for AI agents.
Pricing
from $0.52 / 1,000 results
Rating
0.0
(0)
Developer
Black Falcon Data
Maintained by CommunityActor stats
1
Bookmarked
2
Total users
1
Monthly active users
17 hours ago
Last modified
Categories
Share
What does Google Flights Price Tracker API do?
Google Flights Price Tracker monitors fares on the routes you care about and alerts you when prices move. Run it on a schedule: each run compares against the previous snapshot and returns only NEW / UPDATED / EXPIRED itineraries — each with its price delta versus the last run — and can push a Telegram, Slack, Discord, WhatsApp, or webhook alert. Under the hood it extracts structured itineraries from Google Flights (google.com/travel/flights) — one-way, round-trip, and multi-city — each carrying airline, flight number, departure and arrival times, duration, stops, layover airports, and price in USD. Unique analytics fields — great-circle distance, price-per-km, detour factor, effective speed, and CO₂-per-km — let you rank fares by true value, not just headline price. Expand origin or destination to every airport within a radius, scan a flexible date window for the cheapest day, and opt in to cross-market comparison or through-fare analysis for deeper fare intelligence.
New to Apify? Sign up free and use the included $5 monthly platform credit to test this actor.
Key features
- 🔔 Notifications — Telegram, Slack, Discord, WhatsApp Cloud API, and generic webhook out of the box. Pair with incremental for daily new-listing alerts without pipeline glue.
- 🔁 Price-drop tracking — the core of the tracker. Recurring runs classify every itinerary NEW / UPDATED / EXPIRED and emit only what changed, each with its price delta versus the last run. The first run builds the baseline; every run after is a fare monitor. On by default — and it emits and charges only for changed itineraries, saving 80–95% versus re-pulling everything daily.
- 📐 Distance & value analytics — every itinerary carries computed analytics no other Google Flights actor exposes: great-circle route distance, price-per-km, detour factor (routed vs direct distance through layovers), effective speed, and CO₂-per-km — so you can rank fares by true value.
- 🛫 Multi-airport radius — expand an origin or destination to every airport within a chosen radius (e.g. JFK/LGA/EWR to LAX/BUR/SNA) and fan the search across all combinations, bounded by a cost guard.
- 📅 Cheapest-date scan — scan a ±N-day window around your target date and return the cheapest itinerary per day, each tagged with its scan date — ideal for flexible travellers.
- 🔎 Through-fare data flag (opt-in) — optionally flag a neutral through-fare (connecting vs. direct fare) for fare-structure analysis. Informational only — see the Disclaimer below.
- 💱 Point-of-sale comparison (opt-in) — optionally compare an itinerary across the markets (points of sale) you choose, in one currency. Indicative only — full notes in the Disclaimer below.
- 🛒 Booking options (opt-in) — optionally resolve per-itinerary booking options (airline plus agencies) with per-seller prices and a booking link. Read the Disclaimer before booking. Billed per itinerary resolved.
- 🔗 Paste-mode (URLs in) — paste Google Flights links (a search URL, or a results URL with a
tfsparameter) and the actor fetches each as-is — no need to re-enter origin, destination, or dates. De-duplicated across URLs. - 🔌 MCP connectors — export results into Notion via Apify's MCP connectors — a clean run-summary page, no glue code or AI. Opt in with the App connector field; more destinations open up as Apify's catalog grows.
What data can you extract from Google Flights?
Each itinerary record includes the route (originIata, destIata, outboundDate, optional returnDate), price (priceUsd, currency), carriers (airlines, plus per-segment flightNumber, aircraft, and legroom), timing (durationMinutes and segment departure/arrival times), routing (stops, layoverIatas), and emissions (carbonKg). Every record also carries a human-readable title, the public sourceUrl it came from, and a scrapedAt timestamp. Unique computed analytics — routeDistanceKm, pricePerKm, detourFactor, effectiveSpeedKmh, and co2PerKm — let you rank fares by true value rather than headline price. Incremental runs add a changeType of NEW / UPDATED / UNCHANGED / EXPIRED; the opt-in add-ons attach marketComparison (cross-market point-of-sale prices) and throughFare (a neutral connecting-fare data flag).
Input
Configure the actor through the input schema in Apify Console.
Key parameters:
origin— Origin airport IATA code (e.g., JFK, LAX, LHR)destination— Destination airport IATA code (e.g., LAX, ORD, CDG)outboundDate— Departure date (YYYY-MM-DD format)returnDate— Return date for round-trip flights (YYYY-MM-DD format). Leave empty for one-way.tripType— Type of trip. If omitted and returnDate is set, defaults to round-trip. (default:"one-way")adults— Number of adult passengers (default:1)children— Number of child passengers (default:0)cabinClass— Preferred cabin class (default:"economy")currency— Currency code for prices (default:"USD")market— Market code (e.g., us, gb, de) (default:"us")language— Language code (e.g., en, de, fr) (default:"en")maxItems— Maximum number of results to return. Leave empty for unlimited.- ...and 27 more parameters
Input examples
Cheapest one-way fares on a route — Search a single route for one-way fares. Returns all itineraries sorted by price, with distance analytics.
→ Itinerary records with airline, flight number, departure/arrival times, stops, price in USD, routeDistanceKm, pricePerKm, detourFactor, effectiveSpeedKph, co2PerKm.
{"origin": "JFK","destination": "LAX","outboundDate": "2025-09-15","tripType": "one-way","maxItems": 50}
Round-trip with flexible dates — Scan a ±3-day window around the target dates and return the cheapest itinerary per day combination.
→ One record per day combination, each tagged with its scan date and cheapest total price.
{"origin": "LHR","destination": "NYC","outboundDate": "2025-10-01","returnDate": "2025-10-08","tripType": "round-trip","dateScanDays": 3,"maxItems": 100}
Multi-airport radius search — Expand JFK/LGA/EWR as origins and LAX/BUR/SNA as destinations; fan search across all airport combinations.
→ Itineraries for every origin–destination airport pair within the radius, merged and deduplicated.
{"origin": "JFK","destination": "LAX","originRadiusKm": 60,"destRadiusKm": 60,"outboundDate": "2025-11-20","tripType": "one-way","maxItems": 200}
Price-change monitoring (incremental) — Re-run on a schedule to detect price changes. Each run compares against the previous snapshot.
→ Records tagged NEW / UPDATED / UNCHANGED / EXPIRED — only changed itineraries are pushed.
{"origin": "CPH","destination": "BKK","outboundDate": "2025-12-20","tripType": "one-way","incremental": true,"maxItems": 100}
Paste Google Flights URLs — Paste one or more Google Flights links (a search URL, or a results URL with a tfs parameter) and the actor fetches each as-is — no need to re-enter origin, destination, or dates.
→ Itinerary records parsed from each pasted URL, de-duplicated across URLs.
{"startUrls": ["https://www.google.com/travel/flights/search?tfs=CBwQAhooEgoyMDI2LTA4LTEyagwIAhIIL20vMGYydjByDAgCEggvbS8wMWN4X0ABSAFwAYIBCwj___________8BmAEC&curr=USD&hl=en&gl=us"],"maxItems": 50}
Output
Each run produces a dataset of structured flight records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.
Example flight record
{"itineraryId": "3f2a9c1e7b4d8a6f0c5e2d1b9a8f7e6d5c4b3a2f","tripType": "one-way","originIata": "JFK","destIata": "LAX","outboundDate": "2026-07-22","priceUsd": 199,"currency": "USD","airlines": ["American"],"stops": 0,"durationMinutes": 361,"carbonKg": 215,"segments": [{"airlineCode": "AA","airlineName": "American","flightNumber": "171","fromIata": "JFK","toIata": "LAX","departTime": "08:00","arriveTime": "11:01","durationMinutes": 361,"aircraft": "Airbus A321neo","legroom": "31 in"}],"bookingToken": "CjRIdGZ...","routeDistanceKm": 3974.2,"pricePerKm": 0.05007,"detourFactor": 1,"effectiveSpeedKmh": 660.5,"co2PerKm": 0.05411,"trackedHash": "9a8f7e6d5c4b3a2f1e0d","changeStatus": "NEW"}
Incremental fields
When incremental is enabled, each record carries a changeType field — one of NEW, UPDATED, UNCHANGED, or EXPIRED — computed by comparing against the previous run's snapshot (keyed per search). Default output includes NEW and UPDATED; set emitUnchanged: true to also receive UNCHANGED. EXPIRED records are emitted as lightweight tombstones (carrying the route and date) when a previously seen itinerary disappears.
How to scrape Google Flights
- Go to Google Flights Price Tracker API in Apify Console.
- Configure the input.
- Set
maxItemsto control how many results you need. - Click Start and wait for the run to finish.
- Export the dataset as JSON, CSV, or Excel.
Use cases
- Monitor fares on the routes you care about and get notified when prices drop.
- Rank itineraries by true value using price-per-km and detour factor, not just the headline price.
- Find the cheapest day to fly with a flexible ±N-day date scan.
- Expand a search across every airport within a radius (for example, all New York or all Los Angeles airports) in a single run.
- Build a structured fare dataset for travel analytics, dashboards, or LLM pipelines via MCP export.
How much does it cost to scrape Google Flights?
Google Flights Price Tracker API uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.
- Run start: $0.005 per run
- Per flight (primary event): $0.0008
You are billed only for the events your run actually triggers. Prices below are the Free plan tier; higher Apify plans (Bronze → Diamond) pay progressively less per event, down to roughly 5× lower on the top tier.
| Event | Price (Free tier) | Charged when |
|---|---|---|
| Run start | $0.005 (one-time) | Charged once when the run starts (scales with memory, minimum one). |
| Result (primary) | $0.0008 | Charged per flight itinerary returned. |
| Market compared | $0.0025 | Charged per additional market (point of sale) compared for an itinerary. |
| Through-fare check | $0.0025 | Charged per direct-fare lookup performed for a connecting itinerary. |
| Booking options resolved | $0.005 | Charged per itinerary for which per-seller booking options (airline + agencies) are resolved. |
Example costs (primary event only — other events above add cost when they fire):
- 10 results: $0.013
- 25 results: $0.025
- 100 results: $0.085
- 200 results: $0.17
- 500 results: $0.41
Example: recurring monitoring savings
These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of flights that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.
Example setup: 250 results per run, daily polling (30 runs/month). Event-pricing examples scale linearly with result count.
Numbers below are for the primary Result event. Other events (Market compared, Through-fare check, Booking options resolved) are billed separately when they fire.
| Churn rate | Full re-scrape run cost | Incremental run cost | Savings vs full re-scrape | Monthly cost after baseline |
|---|---|---|---|---|
| 5% — stable niche query | $0.21 | $0.01 | $0.19 (93%) | $0.45 |
| 15% — moderate broad query | $0.21 | $0.04 | $0.17 (83%) | $1.05 |
| 30% — high-volume aggregator | $0.21 | $0.07 | $0.14 (68%) | $1.95 |
Full re-scrape monthly cost at daily polling: $6.15. First month with incremental costs $0.64 / $1.22 / $2.09 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.
Platform usage (compute and proxies) is billed separately by Apify based on actual consumption. Incremental runs consume less on result processing, though fixed per-run overhead stays the same.
FAQ
How many results can I get from Google Flights?
The number of results depends on the search query and available flights on Google Flights. Use the maxItems parameter to control how many results are returned per run.
Does Google Flights Price Tracker API support recurring monitoring?
Yes. Enable incremental mode to only receive new or changed flights on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.
Can I integrate Google Flights Price Tracker API with other apps?
Yes. Google Flights Price Tracker API works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.
Can I use Google Flights Price Tracker API with the Apify API?
Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.
Can I use Google Flights Price Tracker API through an MCP Server?
Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use excludeEmptyFields to keep payloads manageable for LLM context windows.
Is it legal to scrape Google Flights?
This actor extracts publicly available data from Google Flights. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.
Your feedback
If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.
You might also like
- Agoda Reviews Scraper — Hotel Guest Reviews — Scrape guest reviews for any Agoda hotel — star ratings, full review text in the original language.
- Google Flights Scraper API 💰$0.8/1k — 💰$0.8/1k — Scrape Google Flights: fares, routes, layovers, airlines, CO₂. One structured row per.
Getting started with Apify
New to Apify? Create a free account with $5 credit — no credit card required.
- Sign up — $5 platform credit included
- Open this actor and configure your input
- Click Start — export results as JSON, CSV, or Excel
Need more later? See Apify pricing.
Disclaimer
General
This actor is a data and analytics tool. It does not sell, book, or issue tickets, and it is not affiliated with, endorsed by, or acting on behalf of any airline, travel agency, or Google. It uses no airline or agency logos, brand artwork, or affiliation claims, and reproduces only factual carrier names and codes. You are solely responsible for how you use the data this actor provides. Prices and other values are sourced from publicly displayed Google Flights data; they are indicative, point-in-time, and not guaranteed. Verify all fares, fare rules, conditions of carriage, and eligibility directly with the airline or seller before purchasing. Use is at your own risk.
Through-fare / connecting-fare data
The throughFare data flag is a neutral, computed comparison between two publicly displayed Google Flights fares: a connecting itinerary and the direct fare to its connection point. It is provided solely so you can analyse fare structures. Booking a connecting flight with the intention of not flying every segment ("hidden-city" or "throwaway" ticketing) may breach an airline's conditions of carriage. Possible consequences for the traveller include, without limitation: cancellation of all remaining and return segments, denial of boarding, forfeiture of frequent-flyer miles or account closure, recalculation of the fare to the applicable published price, and other penalties at the airline's discretion. Checked baggage is also routed to the ticketed final destination. This actor does not advise, encourage, or instruct any particular booking strategy.
Point-of-sale price comparison
Airfares are priced differently per market (point of sale). When enabled, this actor queries the same itinerary across the markets you select and reports the prices in a single currency for comparison. Reported differences are indicative, point-in-time, and not guaranteed. Booking from a different market may be subject to the airline's or agency's fare rules, residency or payment-method requirements, currency-conversion and foreign-transaction fees, and may not be available to you. Apparent savings may be unavailable or may change by the time you book. This actor reports prices only; it does not book or sell tickets and gives no booking advice.
Booking options
When enabled, this actor resolves, for each itinerary, the booking options (the operating airline plus travel agencies) with their per-seller prices, fare names, and a booking link. Prices are sourced from publicly displayed Google Flights data and may exclude bag fees, seat selection, payment surcharges, or other charges. This actor reports prices and seller names only; it does not book, sell, or issue tickets and gives no booking advice. Verify the final price, fare rules, and availability directly with the seller before purchasing.