Google Flights Scraper — Fares, Airlines, Stops & Times

Search Google Flights by route and date and get clean, structured fares: price, airline, stops, departure/arrival times, total duration and a Google Flights link — for one-way and round-trip trips, any cabin and passenger mix.

How it works & the residential-proxy requirement

Google Flights has no public API and renders its fare list client-side, so this Actor builds the same tfs query the website uses and drives Camoufox (a hardened browser) to render the results page, then reads the flight cards.

Google aggressively blocks datacenter IPs and shows a consent wall on some regions, so a residential proxy is required in practice. The default proxyConfiguration requests Apify's RESIDENTIAL group pinned to US (which also avoids the EU consent wall). Without a residential proxy you'll usually get 0 offers.

What it does

• Search multiple routes in one run (searches list), or a single route via the origin / destination shortcut.
• One-way or round-trip (add returnDate for round-trip).
• Filter by cabin class, max stops, and passenger counts (adults, children, infants).
• Choose currency and market/locale.
• Export to JSON, CSV, or Excel, or pull via the Apify API.

Input

Field	Description
searches	List of routes: { "origin", "destination", "departDate", "returnDate?" } (IATA codes, dates YYYY-MM-DD).
origin / destination / departDate / returnDate	Single-route shortcut instead of searches.
cabinClass	economy / premium-economy / business / first.
maxStops	any / nonstop / one-stop / two-stops.
adults / children / infantsInSeat / infantsOnLap	Passenger counts.
currency	ISO code, e.g. USD, AED, GBP.
market	Google locale, e.g. en-US, en-AE.
maxResultsPerSearch	Cap per route.
proxyConfiguration	Residential proxy recommended (default).

Example

{
  "searches": [
    { "origin": "DXB", "destination": "LHR", "departDate": "2026-10-15", "returnDate": "2026-10-22" },
    { "origin": "AUH", "destination": "JFK", "departDate": "2026-11-01" }
  ],
  "cabinClass": "economy",
  "maxStops": "nonstop",
  "adults": 2,
  "currency": "AED",
  "market": "en-AE",
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Output

Each flight offer is one dataset item:

{
  "origin": "JFK",
  "destination": "LAX",
  "departDate": "2026-10-20",
  "returnDate": null,
  "tripType": "one-way",
  "price": 184,
  "currency": "USD",
  "priceText": "$184",
  "airline": "Delta",
  "stops": "Nonstop",
  "duration": "6 hr 6 min",
  "departure": "Departure time: 9:25 AM.",
  "arrival": "Arrival time: 12:31 PM.",
  "cabinClass": "economy",
  "googleFlightsUrl": "https://www.google.com/travel/flights?tfs=..."
}

Common uses

• Fare monitoring — schedule a run per route and watch for price drops.
• Price comparison — pull many routes/dates in one run.
• Travel dashboards & alerts — feed structured fares into your own tooling.

Notes & limitations

• Residential proxy required in practice — see above. This is inherent to Google Flights, not specific to this Actor.
• Google Flights markup changes often; field parsing is best-effort and degrades gracefully (a field it can't read becomes null rather than failing the run). If Google changes layout, selectors may need an update.
• Prices are indicative "from" fares shown by Google at scrape time and can change before booking.
• Use IATA codes for reliability (DXB, LHR, JFK).