# Flight Price Tracker — fares, price level & history (`lergassy/flight-price-tracker`) Actor \[$0.20/1K rows] Track flight prices on any route: lowest fare, Googles low/typical/high verdict, typical price band and 60 days of price history, one row per run. Many routes in one run, schedule daily, alert on a drop. No run fee, no search fee. - **URL**: https://apify.com/lergassy/flight-price-tracker.md - **Developed by:** [Matvey](https://apify.com/lergassy) (community) - **Categories:** Travel, Agents, MCP servers - **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing from $0.10 / 1,000 rows This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Flight Price Tracker **Flight Price Tracker** watches the routes you care about and tells you, every run, what the cheapest ticket costs right now — and whether that is **low, typical or high** for this route by Google's own measure, with 60 days of price history behind it. Point it at a route, schedule it daily, and alert when the fare drops. **$0.20 per 1,000 rows. No run fee, no search fee, no proxy fee. Error rows are free.** ### What you get on every run | Field | What it is | |---|---| | `lowestPrice` / `currency` | The cheapest ticket Google sells for this route and date | | `priceLevel` | Google's verdict: `low`, `typical` or `high` — this is what turns a number into an alert | | `typicalPriceLow` / `typicalPriceHigh` | What this route normally costs, so you can size the drop | | `priceHistory[]` | 60 days of daily prices — date + price, ready to chart | | `flightsFound` / `cheapestAirline` / `cheapestStops` | Who sells it and whether it is nonstop | | `googleFlightsUrl` | A link that reopens exactly this search, for the alert message | | `scrapedAt` | Timestamp, so a table of runs is already a price history of your own | Switch on the full list and you also get every itinerary — airline, flight numbers, times, aircraft, layovers, CO₂ — but for tracking, one summary row per route per run is all you need, and it is all you pay for. ### How to track a fare 1. Enter **origin** and **destination** as IATA codes (`DPS`, `SIN`, `LHR`) and a **departure date**. Add a **return date** for a round trip — the price is then the total for both directions. 2. Click **Start**. You get one summary row with the lowest price and the price level. 3. Open **Schedules** on this Actor and run it daily. Each run appends a row. 4. Alert when `priceLevel` becomes `low`, or when `lowestPrice` falls below your threshold. #### Many routes in one run Put a list into **routes** and the Actor tracks them all in a single run: ```json { "routes": [ { "origin": "DPS", "destination": "SIN", "departureDate": "2027-03-15" }, { "origin": "DPS", "destination": "KUL", "departureDate": "2027-03-15" }, { "origin": "CGK", "destination": "SIN", "departureDate": "2027-03-16" } ] } ``` Twenty routes checked daily for a month costs a few cents — there is no per-search fee, so the number of routes you watch only affects the rows you keep. ### Alerts in n8n, Make or Zapier Schedule trigger → **Run Actor** with your routes → **IF** `priceLevel = low` or `lowestPrice < threshold` → Slack, Telegram or email with `googleFlightsUrl`. The `run-sync-get-dataset-items` endpoint returns the rows directly, so a single HTTP request is enough if you would rather not use the integration node. ```python from apify_client import ApifyClient client = ApifyClient("") run = client.actor("lergassy/flight-price-tracker").call(run_input={ "routes": [{"origin": "DPS", "destination": "SIN", "departureDate": "2027-03-15"}], }) for row in client.dataset(run["defaultDatasetId"]).iterate_items(): print(row["lowestPrice"], row["currency"], row["priceLevel"]) ``` ### What it costs One event, $0.0002 per row — **$0.20 per 1,000**. Tracking 20 routes every day for a month is 600 rows: **12 cents**. Store tiers pay down to $0.10 per 1,000. Searches, retries, residential proxy and run start are free, and rows that fail are never charged. ### Why prices move, and what `priceLevel` really tells you Airlines reprice several times a day, and the same seat can differ by market and currency. Google compares today's fare to what this route usually costs at this booking lead time; `low` means the current fare sits under that band, which is the signal worth waking up for. A threshold you picked by hand goes stale the moment the route's baseline shifts — the price level does not. ### Notes and limits Times are local to each airport, exactly as Google shows them. Round-trip prices are the total for both directions. A stay longer than about a month returns fewer itineraries, because most airlines cap round-trip stays — track the two legs as one-ways instead. If a search fails after retries, an `error` row explains why and is not charged. The Actor reads publicly displayed prices and schedules without logging in or collecting personal data. Google's terms restrict automated access, and the legality of scraping public data depends on your jurisdiction and use. ### Need something else? Missing a field, need a different alert shape, or want a whole route map swept daily? **Open an issue on this Actor's page** — answered the same day, most requests shipped within a week. Looking for the full search instead of a tracker — every itinerary, the cheapest-dates calendar, booking options with seller prices? That is [Google Flights Scraper](https://apify.com/lergassy/google-flights-scraper). # Actor input Schema ## `origin` (type: `string`): Departure airport code, e.g. DPS (Bali), CGK (Jakarta), SIN (Singapore), LHR (London) ## `destination` (type: `string`): Arrival airport code, e.g. SIN (Singapore), BKK (Bangkok), SYD (Sydney). Ignored when Explore is on. ## `departureDate` (type: `string`): Format YYYY-MM-DD Leave the whole route empty and the Actor runs a demo search so a first run always returns rows. ## `returnDate` (type: `string`): Leave empty for one-way. Format YYYY-MM-DD. Round-trip prices are the total for both directions. ## `adults` (type: `integer`): Passengers aged 12 and over (1–9). Prices are the total for all passengers. ## `children` (type: `integer`): Passengers aged 2 to 11. Google applies child fares where the airline offers them. ## `infantsInSeat` (type: `integer`): Under 2 years old, with their own seat (charged as a child fare on most airlines). ## `infantsOnLap` (type: `integer`): Under 2 years old, travelling on an adult's lap (usually ~10% of the adult fare). ## `cabinClass` (type: `string`): Economy, premium economy, business or first ## `maxStops` (type: `string`): any, 0 nonstop only, 1 up to one stop, 2 up to two stops ## `currency` (type: `string`): ISO code for prices: USD, IDR, EUR, SGD, AUD… ## `market` (type: `string`): Two-letter country code of the point of sale, e.g. US, ID, GB, DE, AU. Google returns the fares, sellers and booking links available to buyers in that country — prices differ by market. Leave empty for Google's default. ## `maxResults` (type: `integer`): Google returns up to ~150 itineraries per search ## `sortBy` (type: `string`): Google's own ranking (best), or by price, duration or departure time ## `calendarDays` (type: `integer`): Lowest fare for each departure date over this many days starting at the departure date — Google's date grid as data. 0 = off, 60 = two months, up to 365. One request per 90 days. Adds calendar\_day items and a calendar.cheapestDates summary to the search item. For round trips the trip length (return minus departure) is kept fixed. ## `resolveBookingOptions` (type: `boolean`): For the top flights of each search, fetch Google's booking options: airline and travel agencies (Trip.com, Expedia, Kiwi…), their prices, fees, and a deep link to book. Round trips need Return flights on — options are fetched for the outbound plus its cheapest return. One extra request per flight — cap it with the field below. ## `resolveReturnFlights` (type: `boolean`): For the top outbound itineraries of a round trip, fetch Google's list of return flights — each with the total price for both directions — so you get complete outbound + return combinations. One extra request per outbound itinerary. ## `exploreAnywhere` (type: `boolean`): Instead of a fixed route, list the cheapest destinations Google suggests from Origin — city, country, price, airline, stops, duration and suggested dates. Uses Departure/Return date when set, otherwise Google's flexible one-week trips over the coming months. ## `routes` (type: `array`): Search many routes in one run. Each item: {"origin": "DPS", "destination": "BKK", "departureDate": "2026-10-15", "returnDate": "2026-10-22"} (returnDate optional). Passengers, cabin and filters below apply to every route. ## `multiCityLegs` (type: `array`): A multi-city trip as a list of legs: {"origin": "SIN", "destination": "BKK", "date": "2026-10-15"}, {"origin": "BKK", "destination": "HKT", "date": "2026-10-19"}, {"origin": "HKT", "destination": "SIN", "date": "2026-10-23"}. Google prices the trip leg by leg; the Actor resolves complete itineraries for the top first-leg options. The total is shown when Google can sell all legs as one ticket. ## `airlines` (type: `array`): IATA airline codes to keep, e.g. SQ, GA, QZ. Leave empty for all. ## `excludeAirlines` (type: `array`): IATA airline codes to drop, e.g. TR (Scoot) ## `maxPrice` (type: `integer`): Drop flights above this price (in the selected currency) ## `maxDurationMinutes` (type: `integer`): Drop itineraries longer than this, e.g. 720 for 12 hours ## `maxLayoverMinutes` (type: `integer`): Drop itineraries with any layover longer than this, e.g. 180 ## `departureTimeFrom` (type: `string`): Earliest departure time, local, e.g. 06:00 ## `departureTimeTo` (type: `string`): Latest departure time, local, e.g. 12:00 ## `arrivalTimeFrom` (type: `string`): Earliest arrival time, local, e.g. 08:00 ## `arrivalTimeTo` (type: `string`): Latest arrival time, local, e.g. 22:00 ## `language` (type: `string`): Language of airport and airline names, e.g. en, id, de ## `calendarOnly` (type: `boolean`): Return just the price calendar and the search summary — the cheapest way to sweep dates or routes. ## `includePriceInsights` (type: `boolean`): Add Google's price level (low / typical / high), typical price range and 60-day price history to the search summary and to every flight ## `includeSearchSummary` (type: `boolean`): Adds one type: "search" row per search with how many itineraries Google had, its own lowest price, the price level and the price history. It is not a flight, so it is off by default and the table stays flights only — the same summary is always saved as the run's SEARCH\_SUMMARY record in the key-value store. ## `maxDestinations` (type: `integer`): How many destinations to return in Explore mode, cheapest first. ## `maxBookingResolutions` (type: `integer`): Per search, counted from the top of the sorted list ## `maxReturnResolutions` (type: `integer`): Per round-trip search, counted from the top of the sorted list ## `maxReturnOptions` (type: `integer`): How many return flights to keep for each outbound itinerary, cheapest first. ## `maxMultiCityResolutions` (type: `integer`): How many first-leg options to follow through all legs (one request per leg each) ## `dataSource` (type: `string`): Auto: Google's results API (full list of 100–150 itineraries, needs a residential proxy) with automatic fallback to the results page (first ~15 itineraries, works from any IP). Force one source for debugging. ## `proxyConfiguration` (type: `object`): Google serves the full results API only to residential IPs — keep Residential proxies for complete results (a search transfers ~250 KB, a fraction of a cent). Datacenter proxies still work through the page fallback with the first ~15 itineraries. ## Actor input object example ```json { "origin": "DPS", "destination": "SIN", "departureDate": "2027-03-15", "adults": 1, "children": 0, "infantsInSeat": 0, "infantsOnLap": 0, "cabinClass": "economy", "maxStops": "any", "currency": "USD", "maxResults": 20, "sortBy": "best", "calendarDays": 0, "resolveBookingOptions": false, "resolveReturnFlights": false, "exploreAnywhere": false, "routes": [], "multiCityLegs": [], "language": "en", "calendarOnly": false, "includePriceInsights": true, "includeSearchSummary": true, "maxDestinations": 60, "maxBookingResolutions": 10, "maxReturnResolutions": 10, "maxReturnOptions": 20, "maxMultiCityResolutions": 5, "dataSource": "auto", "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `flights` (type: `string`): One row per flight itinerary: airline, flight numbers, price in the requested currency, Google's price level against the route's usual band, stops and layovers, times, aircraft, CO₂ and booking options with seller prices. Search summaries, explore destinations and cheapest-date rows share the dataset. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "origin": "DPS", "destination": "SIN", "departureDate": "2027-03-15", "routes": [], "multiCityLegs": [] }; // Run the Actor and wait for it to finish const run = await client.actor("lergassy/flight-price-tracker").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "origin": "DPS", "destination": "SIN", "departureDate": "2027-03-15", "routes": [], "multiCityLegs": [], } # Run the Actor and wait for it to finish run = client.actor("lergassy/flight-price-tracker").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "origin": "DPS", "destination": "SIN", "departureDate": "2027-03-15", "routes": [], "multiCityLegs": [] }' | apify call lergassy/flight-price-tracker --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,lergassy/flight-price-tracker" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/ZSO5876GsNKty2wdE/builds/XWJWBu8ux6KmJX3Um/openapi.json