Search Google Flights
zenserp_flightsDestructive
Google Flights options. Best: origin and destination as 3-letter airport codes plus departure_date (dates and curr are honoured only then). A free-text q or a tfs string from a Google Flights URL also works. SPENDS 1 request of the monthly quota per successful call (failed calls are not charged); do not repeat a call needlessly. GET /v1/flights.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Free-text flight query, used when no airport codes are given (no dates, no curr). | |
| tfs | No | Google Flights search string copied from a Google Flights URL (full filters). | |
| curr | No | 3-letter currency code for the prices, e.g. USD. | |
| cache | No | true = serve a stored copy when one exists (kept 24 h, NOT charged) and store the reply when not. Default false: every call is fetched live and charged. | |
| fields | No | Only return these top-level keys of the reply (for example organic, paid_results, related_searches). Saves context; the call is charged the same. | |
| origin | No | Departure airport code, e.g. JFK. Name one airport, not a city. | |
| destination | No | Arrival airport code, e.g. LHR. | |
| return_date | No | Return date, yyyy-mm-dd. Omit for one-way. | |
| departure_date | No | Departure date, yyyy-mm-dd. Needs origin and destination. |