GET /maps/api/place/queryautocomplete/json

The Query Autocomplete service can be used to provide a query prediction for text-based geographic searches, by returning suggested queries as you type.

The Query Autocomplete service allows you to add on-the-fly geographic query predictions to your application. Instead of searching for a specific location, a user can type in a categorical search, such as "pizza near New York" and the service responds with a list of suggested queries matching the string. As the Query Autocomplete service can match on both full words and substrings, applications can send queries as the user types to provide on-the-fly predictions.

Servers

https://www.googleapis.com
https://maps.googleapis.com
https://roads.googleapis.com

Query parameters

Name	Type	Required	Description
`input`	String	No	(Required) The text string on which to search. The Place Autocomplete service will return candidate matches based on this string and order results based on their perceived relevance.
`location`	String	No	The point around which to retrieve place information. This must be specified as `latitude,longitude`. The `location` parameter may be overriden if the `query` contains an explicit location such as `Market in Barcelona`. Using quotes around the query may also influence the weight given to the `location` and `radius`.
`radius`	String	No	Defines the distance (in meters) within which to return place results. You may bias results to a specified circle by passing a `location` and a `radius` parameter. Doing so instructs the Places service to prefer showing results within that circle; results outside of the defined area may still be displayed. The radius will automatically be clamped to a maximum value depending on the type of search and other parameters. Autocomplete: 50,000 meters Nearby Search: with `keyword` or `name`: 50,000 meters without `keyword` or `name` Up to 50,000 meters, adjusted dynamically based on area density, independent of `rankby` parameter. When using `rankby=distance`, the radius parameter will not be accepted, and will result in an `INVALID_REQUEST`. Query Autocomplete: 50,000 meters Text Search: 50,000 meters
`offset`	String	No	The position, in the input term, of the last character that the service uses to match predictions. For example, if the input is `Google` and the offset is 3, the service will match on `Goo`. The string determined by the offset is matched against the first word in the input term only. For example, if the input term is `Google abc` and the offset is 3, the service will attempt to match against `Goo abc`. If no offset is supplied, the service will use the whole term. The offset should generally be set to the position of the text caret.
`language`	String	No	The language in which to return results. See the list of supported languages. Google often updates the supported languages, so this list may not be exhaustive. If `language` is not supplied, the API attempts to use the preferred language as specified in the `Accept-Language` header. The API does its best to provide a street address that is readable for both the user and locals. To achieve that goal, it returns street addresses in the local language, transliterated to a script readable by the user if necessary, observing the preferred language. All other addresses are returned in the preferred language. Address components are all returned in the same language, which is chosen from the first component. If a name is not available in the preferred language, the API uses the closest match. The preferred language has a small influence on the set of results that the API chooses to return, and the order in which they are returned. The geocoder interprets abbreviations differently depending on language, such as the abbreviations for street types, or synonyms that may be valid in one language but not in another. For example, utca and tér are synonyms for street in Hungarian.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.