# Changelog of Google Flights Scraper - Live Fares, Airlines & Layovers (`sian.agency/google-flights-scraper`) Actor

- **URL**: https://apify.com/sian.agency/google-flights-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/sian.agency/google-flights-scraper.md

## Changelog

All notable changes to the Google Flights Scraper are documented here.

### \[1.0.0] — 2026-09-02

First release.

#### What it does

Searches Google Flights for a route and date and returns up to 32 itineraries, each with the fare
in US dollars, operating airlines, departure and arrival times, total duration, stop count and
full layover detail.

#### User benefits

- **Every connection is described, not just counted.** A row with one stop tells you which airport
  you wait at, in which city, and for how long — so a cheap fare with an eleven-hour layover is
  visible as such before you book rather than after.
- **Filters that actually filter.** Cabin class and a maximum-stops cap narrow the result set at
  the source, so asking for nonstop business class returns the itineraries that exist, not a
  relabelled copy of the economy list.
- **You are billed per itinerary returned.** A route with no flights on your date costs nothing
  beyond the run start, because there is nothing to charge for.
- **Fares are stamped with collection time.** Airfares move by the hour; every row records the
  moment it was read so you always know how stale a price is.
- **One currency throughout.** Everything is quoted in USD, so routes and runs compare directly
  without an exchange-rate step.

#### Use cases

- Fare tracking on a schedule, with enough context per row to tell a real price drop from a worse
  itinerary.
- Airline competitive pricing across every carrier serving a route on a date.
- Travel deal feeds, newsletters and content sites.
- Corporate travel benchmarking before a booking is approved.
- Route and market research — carrier counts, nonstop premiums, connection savings.

#### Known scope

Searches are one direction and one date at a time. Google composes round-trip and multi-city fares
in the browser rather than in the page it serves, so those prices are not available to any
server-side reader. Price a return journey as two separate searches, and treat the total as an
upper bound — published round-trip fares are frequently cheaper than two one-way tickets.