Flight Price Watch — Google Flights Fare Alerts
Pricing
from $1.40 / 1,000 flight records
Flight Price Watch — Google Flights Fare Alerts
Search Google Flights and watch fares for price drops. Give routes and dates; get structured itineraries — or run in watch mode and receive only fare-drop alerts. Built for AI agents: server-callable, pay per record, no start fee.
Pricing
from $1.40 / 1,000 flight records
Rating
0.0
(0)
Developer
Magnova
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Features
Share
Search Google Flights, or watch a fare and get told only when it drops.
Give routes and dates and get structured itineraries: airlines, local departure and arrival times, per-leg detail with layovers, total duration, emissions where Google shows them, and the total fare for your passengers. Run the same input in watch mode on a schedule and the actor remembers the fares — later runs deliver only the itineraries whose price fell, with the previous price and the drop size, plus an optional alert the first time a route's lowest fare crosses your target price.
Built for AI agents and personal assistants: this actor is a Server Actor — call it over plain HTTP with a JSON body and get records back in the response, no run to start and no dataset to poll. It is also available through the Apify MCP server and the official MCP registry listing (search "flight-price-watch").
What you get
FLIGHT records — one per itinerary:
| Field | Meaning |
|---|---|
price, currency | Total fare for the searched passengers, as Google Flights shows it at check time |
airlines | Airline names on the itinerary |
departAt, arriveAt | Local times of the first departure and last arrival |
legs[] | Per-leg from/to airports and names, local times, durationMinutes, aircraft where shown |
layovers[] | Per-connection airport and durationMinutes |
connections, durationMinutes | Connection count and total trip minutes (in-air + layovers) |
emissionsKg, emissionsVsTypicalPercent | Google's emissions estimate, where Google shows it |
googleFlightsUrl | The Google Flights search for this route and dates |
flightKey | Stable identity of the itinerary across watch checks |
In watch mode, FLIGHT records carry a changeType:
BASELINE— delivered on a watch's first check (the current list, charged as flight records)PRICE_DROP— the fare fell since the previous check; addspreviousPrice,dropAmount,dropPercent(charged as a price-drop alert)TARGET_HIT— the route's lowest fare crossed yourtargetPrice(charged as a price-drop alert)
SUMMARY records (never charged) close each route: flights found and delivered, current and previous lowest fares in watch mode, check count. ERROR records (never charged) carry the route and the reason when one route cannot be searched — one bad route never sinks the run.
Pricing
Pay per event, no start fee:
- Flight record — $0.002 (SILVER $0.0017, GOLD+ $0.0014): search results and watch baselines
- Price drop alert — $0.02 (SILVER $0.017, GOLD+ $0.014): PRICE_DROP and TARGET_HIT records
You pay for the drop, not the checking: a watch run where nothing fell delivers only the free SUMMARY and charges nothing. maxTotalChargeUsd caps any run's spend.
Input
| Field | Notes |
|---|---|
routes | Up to 10 × {origin, destination, departureDate, returnDate?} — 3-letter IATA codes, dates as YYYY-MM-DD |
mode | search (default) or watch |
cabinClass | economy, premium_economy, business, first |
adults, children, infantsOnLap | Up to 9 passengers total |
currency | 3-letter code, default USD |
maxResultsPerRoute | Cheapest-first cap per route, 1–50, default 20 |
maxStops | Optional: 0 = nonstop only, 1, 2 |
targetPrice | Watch mode: one alert when the lowest fare reaches it |
minDropPercent, minDropAmount | Watch mode: ignore smaller drops |
maxTotalChargeUsd | Optional hard cap per run |
Example — watch JFK → LAX for a June trip, alert under $150:
{"routes": [{"origin": "JFK", "destination": "LAX", "departureDate": "2027-06-15"}],"mode": "watch","targetPrice": 150,"minDropPercent": 3}
Schedule that input (Apify Schedules, or your own cron calling the API) and each run reports only what changed.
Server mode (for agents)
POST the same JSON input to the actor's server URL:
POST https://magnova--flight-price-watch.apify.actorAuthorization: Bearer <your Apify token>{"routes": [{"origin": "JFK", "destination": "LAX", "departureDate": "2027-06-15"}], "mode": "watch"}
The response carries the records directly: {"records": [...], "summary": {...}}. Watch state persists between calls, so an assistant can register a fare watch once and poll it with the same body — it hears back only when there is news. Up to 5 routes per server request.
Notes and limits
- Round-trip prices are Google's full round-trip fares; the leg detail, times and duration describe the outbound journey.
- Public Google Flights data only, read logged out — no account, no cookies, no booking. This actor finds and watches fares; it does not book.
- Fares are exactly as Google Flights displays them at check time and can change at any time; the booking link is the Google Flights search for the route.
- Google Flights covers roughly the next 330 days; dates beyond that return an ERROR record for that route.
- Searches are paced and retried automatically — Google rate-limits rapid repeats, so a 10-route run takes under a minute.
- A watch is identified by route + dates + cabin + passengers + currency. Change any of them and it starts a fresh baseline.