Searching for places
Basic example
To search for places around a set of geographic coordinates, use the /realtime/serp endpoint and set search_engine to google_maps_search, as in the example below:
curl --location --request POST 'https://api.webit.live/api/v1/realtime/serp' \
--header 'Authorization: Basic <credential string>' \
--header 'Content-Type: application/json' \
--data-raw '{
"search_engine": "google_maps_search",
"query": "Cinema",
"coordinates": {
"latitude": "40.7123695",
"longitude": "-74.0357317"
}
}'import requests
url = 'https://api.webit.live/api/v1/realtime/serp'
headers = {
'Authorization': 'Basic <credential string>',
'Content-Type': 'application/json'
}
data = {
"search_engine": "google_maps_search",
"query": "Cinema",
"coordinates": {
"latitude": "40.7123695",
"longitude": "-74.0357317"
}
}
response = requests.post(url, headers=headers, json=data)
print(response.status_code)
print(response.json())
Request options
query
Required
String
The term or phrase to search for.
search_engine
Required
Enum: google_maps_search | google_maps_place | google_maps_reviews
The search engine from which to collect results.
coordinates
Optional
String or Object "@{latitude},{longitude},{zoom}z"
The coordinates to target. When using a string, zoom is required.
"coordinates": { "latitude": "40.7590562", "longitude": "-74.0042502", "zoom": "14" }
When using an object, zoom is optional.
offset
Optional
Integer
Offset the pagination position by this number of listings (eg: 20).
domain
Optional
String
Search through a custom top-level domain of Google. eg: "co.uk"
country
Optional (default = all)
String
Country used to access the target URL, use ISO Alpha-2 Country Codes i.e. US, DE, GB
locale
Optional (default = en)
String
String | LCID standard locale used for the URL request. Alternatively, user can use auto for automatic locale based on country targeting.
parse
Optional (default = true)
Enum: true | false
Instructs Nimble whether to structure the results into a JSON format or return the raw HTML.
Response
200 - OK
If the request is executed successfully and parsing is either omitted or set to true, the output will resemble the example below:
Using reviews, place, and next_page links.
A successful result includes a number of follow-up links that can be used to get more information or browse through pagination. These include:
500 Error
400 Input Error
Response Codes
200
OK.
400
The requested resource could not be reached.
401
Unauthorized/invalid credental string.
500
Internal service error.
501
An error was encountered by the proxy service.
Last updated
