Google Flights scrapers compared

Platform accounting charge, applied per row stored in the dataset.

• Page Processed (page_processed)
• Setup (setup)
• Booking Options Processed (booking_option_processed)

One itinerary, price-calendar day or explore destination row. Error rows and empty results are always free. No run fee, no search fee, no proxy fee.

Single result in the default dataset.

• Additional data (additional-data)

Single result in the default dataset.

• Flight lookup (flight_search)

Charged per flight option extracted from Google Flights.

• Run started (start)

Each flight option delivered to the dataset.

• Search (search)
• Browser search (browser-search)
• Booking options (booking-options)
• Return flights (return-flights)
• Price graph day (price-graph-day)
• Explore destination (explore-destination)

One route quote with carrier, departure and return dates, cabin, total price, price per passenger, stops, duration, and the departure and arrival airports and times. Every row returned is charged; a run that returns no rows is free.

Single result in the default dataset.

• Per successful search (flight-search)
• Filter used (filter)
• Per-itinerary booking option (additional-detail)

One result row — itinerary, calendar date, destination or search summary. Error rows and empty results are always free. No run fee, no search fee, no proxy fee.

Charged once per successful Google Flights search.

• Flight itinerary returned (flight-result)

Single result in the default dataset.

• Itinerary Scraped (itinerary-scraped)

One search for a route and date, with every flight it returns included. There is no per-result charge, so a route with 143 flights costs the same as one with 8.

• Actor start (actor_start)
• Return flights per outbound (return_flights)

One flight option delivered. Searches that fail or return nothing are never charged.

Single result in the default dataset.

• Setup (One-time Fee) (setup-fee)
• Page processed (page-processed)

One row delivered to the dataset: a flight itinerary (with price, airline, stops, duration, times and segments) in search mode, or one priced departure date in price calendar mode.

Each flight option (or return option) written to the dataset, with price, airlines, times, stops, layovers, amenities, CO2 and price insights.

• Booking options (booking-options)
• Price graph date (price-graph-date)

One route and departure date (or round trip, or multi-city trip): all flights Google shows, with price insights. Also charged in price-monitoring mode, whether or not the price changed.

• Calendar day (calendar-day)
• Return flights (return-flights)
• Booking options (booking-options)

Single result in the default dataset.

• Flight search page completed (page_processed)
• Direct booking link resolved (booking_option_processed)

One flight itinerary (with its return flight on round trips).

• Price-calendar date (calendar-date)

One Google Flights itinerary row pushed to the dataset (price, segments, times, CO2, and related fields).

• Calendar date (calendar-date)

Charged per item scraped.

One flight option: price, airline(s), stops, departure/arrival airports, times & dates, total duration and baggage.

• Price insight scraped (priceInsight)

One route across the dates searched: the fare calendar, cheapest date and flight, cheapest nonstop, fastest option, airline prices, cheapest weekday, and Google's price level, 60-day price history and booking tip.

• Flight (flight)

A date is returned in your table.

• Round-trip date grid built (date-grid-built)

One row for a flight Google Flights lists for the searched route and departure date, with price, times, stops, layovers, legs and CO2. With Monitor on, only flights that are new or whose price moved since the last run. Rows that say there are no flights, no change, more flights than asked for, an input Google did not accept, a page that could not be read or that the run hit its limit are free.

• Run start (actor-start)

One flight is added to your results.

• Route and date searched (route-date-searched)

Charged per itinerary whose sellers are looked up.

• actor-start (actor-start)
• offer-scraped (offer-scraped)

One departure day delivered with its cheapest fare. Days without any flight and routes that fail are never charged.

Each flight result returned

Single result in the default dataset.

• Market compared (market_compared)
• Through-fare check (through_fare_check)
• Booking options resolved (booking_options_resolved)

Single result in the default dataset.

• Market compared (market_compared)
• Through-fare check (through_fare_check)
• Booking options resolved (booking_options_resolved)

Charged automatically for each item pushed to the default dataset.

• Route scanned (route-scanned)

One flight option saved to the dataset.

One flight with price, legs, layovers and price insights

• Booking options (booking-options)
• Calendar date (calendar-date)
• Explore destination (explore-destination)

One route + date searched

• Flight (flight)
• Return options (return-options)

One dataset item written via the default (non-PPE) push path.

• Itinerary (flight-result)

One completed Google Flights search (a route and its dates) that returned flights, including Google's price insights (price level, typical price range, 60-day price history). Charged once per search, also on scheduled runs that output only changes.

• Itinerary (result)
• Booking options (booking-options)

Charged for each flight option saved: price, airlines, flight numbers, times, stops, layovers, duration and emissions.

• Search (search)

One row of an itinerary Google listed for a search: the flights, times with offsets, duration, stops and layovers, aircraft, legroom, amenities, CO2, bags, the exact fare and served currency, the booking token and link, the price insight. The free search summary row, a search Google lists no flights for, a refused or invalid search and a list in another currency than the one asked are never charged.

• Booking options of an itinerary (booking_options)
• Price calendar day (calendar_day)
• Explore destination (destination)

One itinerary with a fare. Flights Google lists without a price, and routes that return nothing, are free.

• Run start (actor-start)

One flight, route summary (price insights) or price-calendar day delivered. Failed searches and routes without flights are not charged.

One charge for a unique route/date query that writes at least one validated flight option, including partial searches with usable results. Empty, failed and skipped searches are not charged.

One flight from the results: price, airlines, times, duration, stops, layovers, bags, CO2 emissions.

One flight option with its price, airlines, stops and times.

One flight itinerary for your route, dates, cabin and passengers: price for all passengers, airline, departure and arrival times, duration, stops, layovers, CO2 (row keys route, origin, destination, depart_date, return_date, seat, adults, price, currency, airline, stops, depart_time, arrive_time, duration_minutes, layovers, co2_kg, rank, google_url): $5 per 1,000 itineraries. Usually 10 to 35 rows per route and date; maxResultsPerSearch caps them. Not charged: empty or failed searches, duplicates (an itinerary two overlapping searches both return is billed once), status rows, refused inputs. No start fee; proxy and compute are included in the event price. The run stops at the maximum cost per run you set when starting it (Apify run option maxTotalChargeUsd), never above it.

Charged once for each flight itinerary row delivered (outbound or return). Searches Google has no flights for cost nothing beyond the run start.

• Cheapest-date calendar day (cheapest-date)
• Actor start (actor-start)

One priced Google Flights itinerary written to the dataset.

Single result in the default dataset.