Google Flights Scraper 💰$0.8/1k
Pricing
from $0.52 / 1,000 results
💰$0.8/1k — Scrape Google Flights: fares, routes, layovers, airlines, CO₂. One structured row per itinerary (JSON/CSV). Track price changes across runs, expand to nearby airports & flexible dates, resolve per-seller booking options. API + MCP for AI agents.
Return date for round-trip flights (YYYY-MM-DD format). Leave empty for one-way.
Type of trip. If omitted and returnDate is set, defaults to round-trip.
Preferred cabin class
Maximum number of results to return. Leave empty for unlimited.
Drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards.
Hard cap on total searches after fan-out (radius × dates × batch).
Hard cap on opt-in add-on lookups (market compare / through-fare / booking options).
Paste one or more Google Flights links (a search URL or a results URL with a tfs parameter). Each is fetched as-is and its itineraries are returned — origin, destination, and date are not required when you use this. Accepts a list of URL strings.
Track NEW / UPDATED / EXPIRED itineraries across runs (price-drop detection).
Also output itineraries whose tracked fields did not change since the last run.
Optional. Pin a name to share one incremental tracking history across runs. Leave empty and each distinct search keeps its own isolated history automatically.
Expand the origin to all airports within this many km (0 = origin only).
Expand the destination to all airports within this many km (0 = destination only).
Scan ±N days around the outbound date and return the cheapest itinerary per day (0 = off).
Re-query each itinerary in these markets and attach a point-of-sale price comparison. Billed per extra market. INDICATIVE ONLY — see README; this actor reports prices only and books nothing.
For connecting itineraries, look up the direct fare to the connection point and attach a NEUTRAL comparison flag. INFORMATIONAL ONLY — see README; no booking advice, books/sells nothing, no airline branding.
For each itinerary, resolve the per-seller booking options (airline + travel agencies) with their prices, fare names, and a booking link. Billed per itinerary resolved. INFORMATIONAL ONLY — see README; prices are indicative, this actor books/sells nothing and uses no airline or agency branding.
Telegram bot token (from @BotFather). Required for Telegram notifications.
Telegram chat or channel ID where alerts are sent.
WhatsApp Business phone number ID from Meta Business Manager.
Meta Cloud API access token with whatsapp_business_messaging scope.
Recipient phone number in E.164 format (e.g. +14155551234).
Universal escape hatch for n8n / Make / Zapier / custom HTTP backends. Receives a JSON POST per run.
Additional HTTP headers sent with the generic webhook POST.
Maximum number of itineraries included in each notification message (1–20).
When Incremental tracking is on, only notify for NEW and UPDATED itineraries.
Optional. Pick a connected app under Settings → API & Integrations to receive your results. A run-summary is written to the connected app; support is best-effort as Apify expands its connector catalog.
