> For the complete documentation index, see [llms.txt](https://help.netnut.io/netnut-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.netnut.io/netnut-documentation/netnut-scraper-apis/serp-api/google-scraper/google-flights/features.md). # Features ## Google Flights Parameters ### Origin and Destination #### Origin Defines the departure location for the flight search. Accepts a city name, airport code, or region. **Parameter** `flightFrom: string` **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv ``` **Use Cases** * Search flights from a specific city or airport * Use IATA codes for precise origin matching (e.g., `JFK`, `EWR`, `LGA`) * Regional searches using city or area names *** #### Destination Defines the arrival location for the flight search. Accepts a city name, airport code, or region. **Parameter** `flightTo: string` **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv ``` **Use Cases** * Search flights to a specific city or airport * Use IATA codes for precise destination matching (e.g., `LAX`, `LHR`, `TLV`) * Regional destination searches *** #### Route Defines a full origin-to-destination route by combining both location parameters. **Parameters** `flightFrom: string` `flightTo: string` **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv ``` **Use Cases** * Full route-based flight searches * Price monitoring between city pairs * Competitive fare analysis across carriers on a single route *** ### Dates #### Departure Date Defines the outbound flight date. The value must be sent in `YYYY-MM-DD` format. **Parameter** `departureTime: string` **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv&departureTime=2026-06-01 ``` **Use Cases** * Date-specific flight availability * Future travel planning * Fare trend analysis by departure date *** #### Return Date Defines the return flight date for round-trip searches. The value must be sent in `YYYY-MM-DD` format. Omit this parameter for one-way searches. **Parameter** `returnTime: string` **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv&departureTime=2026-06-01&returnTime=2026-06-05 ``` **Use Cases** * Round-trip itinerary searches * Stay-length comparisons * Travel package pricing *** #### Round-Trip Dates Defines a complete round-trip itinerary by combining departure and return dates. **Parameters** `departureTime: string` `returnTime: string` **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv&departureTime=2026-06-01&returnTime=2026-06-05 ``` **Use Cases** * Full round-trip fare retrieval * Flexible date comparison across date ranges * Accurate itinerary pricing for travel applications *** ### Passengers #### Adults Defines the number of adult passengers. **Parameter** `adults: integer` **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv&departureTime=2026-06-01&adults=3 ``` **Use Cases** * Solo traveler searches * Couple and group fare lookups * Passenger-aware pricing *** ### Currency Defines the currency used for flight prices in the results. **Parameter** `currency: string` **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=lax&departureTime=2026-06-01¤cy=ILS ``` **Use Cases** * Normalize flight pricing across regions * Compare fares in a target currency * Localized travel pricing analysis *** ### Raw HTML Controls whether raw HTML is included in the response alongside the parsed JSON. **Parameter** `rawHtml: integer` **Values** | Value | Behavior | | ----------- | ------------------------------------- | | *(omitted)* | Returns parsed JSON only (default) | | `1` | Returns both parsed JSON and raw HTML | | `2` | Returns raw HTML only | **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv&departureTime=2026-06-01&rawHtml=1 ``` **Use Cases** * Access the full rendered page alongside structured data * Debug or validate parsed output against the source HTML * Extract custom fields not included in the default JSON response *** ### Combined Example You can combine multiple parameters to create a more precise Google Flights search. **Example** ``` https://serp-api.netnut.io/search?engine=google_flights&flightFrom=ny&flightTo=tel-aviv&departureTime=2026-06-01&returnTime=2026-06-05&adults=3¤cy=ILS&rawHtml=1 ``` This request will: * Search Google Flights from New York to Tel Aviv * Set a round-trip from June 1 to June 5, 2026 * Search for 3 adult passengers * Return prices in ILS * Return both parsed JSON and raw HTML --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.netnut.io/netnut-documentation/netnut-scraper-apis/serp-api/google-scraper/google-flights/features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.