Google Flights Search (Real-Time Fares)

FlightPowers one-way fare search: live prices read from Google Flights. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- plus either one departure date or a date range. Returns each flight's price, airline, duration, stops, a bookable buy_link, and Google's historical price range (price_insights_low / price_insights_high), the band that shows whether a fare is actually a good deal.

Suited to any one-way fare question, including open-ended ones. One call accepts a date range and several destinations and searches every combination: 'Cheapest flight to Sri Lanka anywhere in October' is one call, not thirty. That holds with the caller's own key. On the free sign-in allowance (10 searches a day, one per combination) a grid larger than what is left today is refused before anything runs; a grid within what is left runs, and a whole-month scan needs the caller's own key.

Each date/destination combination is one search; the count comes back in api_usage.

by_destination carries one entry per requested destination -- empty ones included, each with a reason that separates a destination with no flights from one that was not searched, whose search failed, or whose fares did not fit in limit.

Fares go stale within minutes: a current price comes from a new search, not from an earlier result.

FlightPowers round-trip fare search: live prices read from Google Flights, priced as paired legs rather than two separate one-ways. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- a departure date or range, and either a return date or a trip length in nights. Returns the total price for both legs, per-leg airline, stops and duration, and a single bookable buy_link for the trip.

Suited to any return-trip fare question. A flexible search is ONE call: departure_date_from / departure_date_to set the outbound range and nights, in place of return_date, compares trip lengths -- '5 to 7 nights in Rome sometime in May' is one call.

A WHOLE MONTH is one call too. departure_date_from "2026-10-01", departure_date_to "2026-10-31" and nights [3, 4, 5] prices every departure day in October at three trip lengths and shows which combination is cheapest. That is 93 date/night combinations and the cap rises to cover them by itself, so the whole grid runs in that one call. That holds with the caller's own key. On the free sign-in allowance (10 searches a day, one per combination) a grid larger than what is left today is refused before anything runs; a grid within what is left runs, and a whole-month scan needs the caller's own key.

Each date/night/destination combination is ONE search, so a month at three trip lengths is 93 of them and the same month across two destinations is 186. A search that fails with a server error is retried once, so with the caller's own key the figure the plan is charged is api_usage.hub_requests_billed (retries included), not the combination count.

by_destination carries one entry per requested destination -- empty ones included, each with a reason that separates a destination with no flights from one that was not searched, whose search failed, or whose fares did not fit in limit.

Fares go stale within minutes: a current price comes from a new search, not from an earlier result.