Google Travel Explore Destination
The flight options to one destination on the dates Google's Explore map lists for it (or on dates given), as Google ranks them, answered as the document with `departure_date`, `return_date` and `flights`.
The flight options to one destination on the dates Google's Explore map lists for it (or on dates
given), as Google ranks them, answered as the document with departure_date, return_date and
flights. It makes two calls the page does make: Explore's map for
the dates it lists for the place, then Google Flights' for that route on those dates; each option
is an itinerary of the second and price is the whole trip's. A place that is not on the map (an
airport code, a small town) gets dates 30 and 37 days from today; a map place id (/m/...) is
needed to get Explore's dates. Refused (400): the named time periods
(weekend_trip_in_...), travel_mode, max_flight_duration, carry_on_bags,
included_airlines.
X-API-Key<token>Your API key.
cancel_token?stringA name you make up for this request (a UUID is fine), so you can later GET /v1/cancel
with it. Only you know it, so only you can cancel. Use a new one for every request, retries included: a cancelled token stays cancelled for a few minutes.
1 <= length <= 128departure_id*stringAirport code or place id.
arrival_id*stringAirport code or place id.
time_period?stringDefault: Explore's own dates. A date (YYYY-MM-DD, one way) or a range (YYYY-MM-DD..YYYY-MM-DD, round trip).
flight_type?string"round_trip""round_trip""one_way"adults?integer1 <= value1children?integer0 <= value0infants_in_seat?integer0 <= value0infants_on_lap?integer0 <= value0travel_class?string"economy""economy""premium_economy""business""first_class"stops?string"any""any""nonstop""one_stop_or_fewer""two_stops_or_fewer"max_price?integercurrency?string"USD"hl?string"en"gl?string"us"The options, as the document. When the page could not be parsed, the usual envelope.
application/json- response
The first three keys of every parsed 200 (the answer is the document itself, no success/data
envelope): what the search was (search_metadata), what it asked (search_parameters), the
parser's own search_information ({} when it has none). The engine's blocks follow, at the same
level. An engine whose answer is a list puts it under results.
search_metadata*search_parameters*The request's own fields as sent, engine first, without cancel_token.
search_information*The parser's own, e.g. yelp_search's; otherwise {}.
departure_date?stringdatereturn_date?stringdateflights?array<>[key: string]?anycurl -X GET 'https://api.justserp.com/v1/google/travel-explore/destination?departure_id=%2Fm%2F02_286&arrival_id=%2Fm%2F05qtj'{ "search_metadata": { "id": "string", "status": "Success", "created_at": "string", "request_url": "string", "html_url": "string" }, "search_parameters": {}, "search_information": {}, "departure_date": "2019-08-24", "return_date": "2019-08-24", "flights": [ { "position": 0, "price": 0, "airline_code": "string", "airline": "string", "stops": 0, "departure_date": "2019-08-24", "departure_airport": { "id": "string", "name": "string" }, "arrival_airport": { "id": "string", "name": "string" }, "flight_duration": "string", "duration": 0 } ]}Google Travel Explore GET
The destinations on Google's Explore map for a departure place, each with the cheapest flight and the dates it is for, answered as the document with `destinations` (47 to 55 places seen).
Google Maps Directions GET
The routes between two places, with the time each travel mode takes, answered as the document: `search_metadata`, `search_parameters` (the request as read, with the defaults), `search_information` (`{}`), `travel_modes`, `places_info` and `directions`.