JustSERPDocs
Google

Google Travel Explore

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).

GET
/v1/google/travel-explore

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). Only places with a flight are listed. A round trip is a week in the next six months, as Google chooses. Refused (400): arrival_id, time_period, interests, travel_mode other than all, max_flight_duration, carry_on_bags, included_airlines. Not answered: avg_cost_per_night, distance, the driving duration. Google's "internal error" is retried; a captcha (/sorry/) is captcha.

Authorization

headerX-API-Key<token>

Your API key.

Query Parameters

cancel_token?string

A 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.

Length1 <= length <= 128
departure_id*string

Airport code or place id; up to 10.

flight_type?string
Default"round_trip"
Value in"round_trip""one_way"
adults?integer
Range1 <= value
Default1
children?integer
Range0 <= value
Default0
infants_in_seat?integer
Range0 <= value
Default0
infants_on_lap?integer
Range0 <= value
Default0
travel_class?string
Default"economy"
Value in"economy""premium_economy""business""first_class"
stops?string
Default"any"
Value in"any""nonstop""one_stop_or_fewer""two_stops_or_fewer"
max_price?integer
currency?string
Default"USD"
hl?string
Default"en"
gl?string
Default"us"

Response Body

The destinations, as the document. When the page could not be parsed, the usual envelope.

application/json
  1. 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 {}.

destinations?array<>
[key: string]?any
Example Request
curl -X GET 'https://api.justserp.com/v1/google/travel-explore?departure_id=%2Fm%2F02_286&stops=nonstop&max_price=400'
Example Response
{  "search_metadata": {    "id": "string",    "status": "Success",    "created_at": "string",    "request_url": "string",    "html_url": "string"  },  "search_parameters": {},  "search_information": {},  "destinations": [    {      "name": "string",      "kgmid": "string",      "primary_airport": "string",      "country": "string",      "coordinates": [        0,        0      ],      "outbound_date": "2019-08-24",      "return_date": "2019-08-24",      "alternative_outbound_date": "2019-08-24",      "image": "string",      "flight": {        "airport_code": "string",        "price": 0,        "stops": 0,        "flight_duration": "string",        "flight_duration_minutes": 0,        "airline_code": "string",        "airline_name": "string",        "departure_city_kgmid": "string"      }    }  ]}

Google Hotels Autocomplete GET

What the Google Hotels search box suggests for some typed letters, answered as the document with `suggestions`: five at most, places (`destination`) and hotels (`hotel`).

Google Travel Explore Destination GET

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`.