Stay organized with collections Save and categorize content based on your preferences.
Note: Server-side and client-side librariesThe Places API is also available with the Java Client, Python Client, Go Client and Node.js Client for Google Maps Services. The Places API and the client libraries are for use in server applications.
If you're building a client-side application, take a look at the Places SDK for Android (New), the Places SDK for iOS (New), and the Places Library, Maps JavaScript API.
Place Autocomplete (Legacy) is a web service that returns place predictions in response to an HTTP request. The request specifies a textual search string and optional geographic bounds. The service can be used to provide autocomplete functionality for text-based geographic searches, by returning places such as businesses, addresses and points of interest as a user types.
Place Autocomplete (Legacy) requestsPlace Autocomplete (Legacy) is part of the Places API and shares an API key and quotas with the Places API.
Note: You can use Place Autocomplete (Legacy) even without a map. If you do show a map, it must be a Google map. When you display predictions from Place Autocomplete (Legacy) without a map, you must include the Google logo displayed inline with the search field/results. For more information, see Displaying the Google logo and attributions.Place Autocomplete (Legacy) can match on full words and substrings, resolving place names, addresses, and plus codes. Applications can therefore send queries as the user types, to provide on-the-fly place predictions.
You must properly format plus codes. This means you must URL-escape the plus sign to %2B, and you must URL-escape spaces to %20.
849VCWC8+R9 is 849VCWC8%2BR9.CWC8+R9 Mountain View, CA, USA is CWC8%2BR9%20Mountain%20View%20CA%20USA.The returned predictions are designed to be presented to the user to aid them in selecting the place they want. You can send a Place Details (Legacy) request for more information about any of the places which are returned.
A Place Autocomplete (Legacy) request is an HTTP URL of the following form:
https://maps.googleapis.com/maps/api/place/autocomplete/output?parameters
where output may be either of the following values:
json (recommended) indicates output in JavaScript Object Notation (JSON)xml indicates output as XMLCertain parameters are required to initiate a Place Autocomplete (Legacy) request. As is standard in URLs, all parameters are separated using the ampersand (&) character. The list of parameters and their possible values are enumerated below.
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.
A grouping of places to which you would like to restrict your results. Currently, you can use components to filter by up to 5 countries. Countries must be passed as a two character, ISO 3166-1 Alpha-2 compatible country code. For example: components=country:fr would restrict your results to places within France. Multiple countries must be passed as multiple country:XX filters, with the pipe character | as a separator. For example: components=country:us|country:pr|country:vi|country:gu|country:mp would restrict your results to places within the United States and its unincorporated organized territories.
The language in which to return results.
language is not supplied, the API attempts to use the preferred language as specified in the Accept-Language header.The point around which to retrieve place information. This must be specified as latitude,longitude. The radius parameter must also be provided when specifying a location. If radius is not provided, the location parameter is ignored.
When using the Text Search API, the `location` parameter may be overriden if the `query` contains an explicit location such as `Market in Barcelona`.
Prefer results in a specified area, by specifying either a radius plus lat/lng, or two lat/lng pairs representing the points of a rectangle. If this parameter is not specified, the API uses IP address biasing by default.
ipbias (this option has no additional parameters).circle:radius@lat,lng.rectangle:south,west|north,east. Note that east/west values are wrapped to the range -180, 180, and north/south values are clamped to the range -90, 90.Restrict results to a specified area, by specifying either a radius plus lat/lng, or two lat/lng pairs representing the points of a rectangle.
circle:radius@lat,lng.rectangle:south,west|north,east. Note that east/west values are wrapped to the range -180, 180, and north/south values are clamped to the range -90, 90.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.
The origin point from which to calculate straight-line distance to the destination (returned as distance_meters). If this value is omitted, straight-line distance will not be returned. Must be specified as latitude,longitude.
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.
keyword or name: 50,000 meterskeyword or name
rankby parameter.rankby=distance, the radius parameter will not be accepted, and will result in an INVALID_REQUEST.The region code, specified as a ccTLD ("top-level domain") two-character value. Most ccTLD codes are identical to ISO 3166-1 codes, with some notable exceptions. For example, the United Kingdom's ccTLD is "uk" (.co.uk) while its ISO 3166-1 code is "gb" (technically for the entity of "The United Kingdom of Great Britain and Northern Ireland").
A random string which identifies an autocomplete session for billing purposes.
The session begins when the user starts typing a query, and concludes when they select a place and a call to Place Details is made. Each session can have multiple queries, followed by one place selection. The API key(s) used for each request within a session must belong to the same Google Cloud Console project. Once a session has concluded, the token is no longer valid; your app must generate a fresh token for each session. If the sessiontoken parameter is omitted, or if you reuse a session token, the session is charged as if no session token was provided (each request is billed separately).
We recommend the following guidelines:
Returns only those places that are strictly within the region defined by location and radius. This is a restriction, rather than a bias, meaning that results outside this region will not be returned even if they match the user input.
You can restrict results from a Place Autocomplete request to be of a certain type by passing the types parameter. This parameter specifies a type or a type collection, as listed in Place Types. If nothing is specified, all types are returned.
A place can only have a single primary type from types listed in Table 1 or Table 2. For example, a hotel where food is served may by returned only with types=lodging and not with types=restaurant.
For the value of the types parameter you can specify either:
Up to five values from Table 1 or Table 2. For multiple values, separate each value with a | (vertical bar). For example:
types=book_store|cafe
Any single supported filter in Table 3. You cannot mix type collections.
geocode and establishment are part of Table 2, they cannot be combined with any other type in Tables 1, 2, or 3 in Place Autocomplete request filters.
The request will be rejected with an INVALID_REQUEST error if:
types parameter only works on the primary type of the place, not all types associated with the place. Although every place has a primary type, not every primary type is supported by Places API (New). Supported types include those listed in Table 1 or Table 2.A request for establishments containing the string "Amoeba" within an area centered in San Francisco, CA:
URLhttps://maps.googleapis.com/maps/api/place/autocomplete/json ?input=amoeba &location=37.76999%2C-122.44696 &radius=500 &types=establishment &key=YOUR_API_KEYcURL
curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=amoeba&types=establishment&location=37.76999%2C-122.44696&radius=500&key=YOUR_API_KEY'
The same request, restricted to results within 500 meters of Ashbury St & Haight St, San Francisco:
URLhttps://maps.googleapis.com/maps/api/place/autocomplete/json ?input=amoeba &location=37.76999%2C-122.44696 &radius=500 &strictbounds=true &types=establishment &key=YOUR_API_KEYcURL
curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=amoeba&types=establishment&location=37.76999%2C-122.44696&radius=500&strictbounds=true&key=YOUR_API_KEY'
A request for addresses containing "Vict" with results in French:
URLhttps://maps.googleapis.com/maps/api/place/autocomplete/json ?input=Vict &language=fr &types=geocode &key=YOUR_API_KEYcURL
curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=Vict&types=geocode&language=fr&key=YOUR_API_KEY'
A request for cities containing "Vict" with results in Brazilian Portuguese:
URLhttps://maps.googleapis.com/maps/api/place/autocomplete/json ?input=Vict &language=pt_BR &types=%28cities%29 &key=YOUR_API_KEYcURL
curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=Vict&types=(cities)&language=pt_BR&key=YOUR_API_KEY'
Note that you'll need to replace the API key in these examples with your own key.
Place Autocomplete (Legacy) responsePlace Autocomplete (Legacy) responses are returned in the format indicated by the output flag within the request's URL path. The results below are indicative of what may be returned for a query with the following parameters:
https://maps.googleapis.com/maps/api/place/autocomplete/json ?input=Paris &types=geocode &key=YOUR_API_KEYcURL
curl -L -X GET 'https://maps.googleapis.com/maps/api/place/autocomplete/json?input=Paris&types=geocode&key=YOUR_API_KEY'JSON
{
"predictions":
[
{
"description": "Paris, France",
"matched_substrings": [{ "length": 5, "offset": 0 }],
"place_id": "ChIJD7fiBh9u5kcRYJSMaMOCCwQ",
"reference": "ChIJD7fiBh9u5kcRYJSMaMOCCwQ",
"structured_formatting":
{
"main_text": "Paris",
"main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
"secondary_text": "France",
},
"terms":
[
{ "offset": 0, "value": "Paris" },
{ "offset": 7, "value": "France" },
],
"types": ["locality", "political", "geocode"],
},
{
"description": "Paris, TX, USA",
"matched_substrings": [{ "length": 5, "offset": 0 }],
"place_id": "ChIJmysnFgZYSoYRSfPTL2YJuck",
"reference": "ChIJmysnFgZYSoYRSfPTL2YJuck",
"structured_formatting":
{
"main_text": "Paris",
"main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
"secondary_text": "TX, USA",
},
"terms":
[
{ "offset": 0, "value": "Paris" },
{ "offset": 7, "value": "TX" },
{ "offset": 11, "value": "USA" },
],
"types": ["locality", "political", "geocode"],
},
{
"description": "Paris, TN, USA",
"matched_substrings": [{ "length": 5, "offset": 0 }],
"place_id": "ChIJ4zHP-Sije4gRBDEsVxunOWg",
"reference": "ChIJ4zHP-Sije4gRBDEsVxunOWg",
"structured_formatting":
{
"main_text": "Paris",
"main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
"secondary_text": "TN, USA",
},
"terms":
[
{ "offset": 0, "value": "Paris" },
{ "offset": 7, "value": "TN" },
{ "offset": 11, "value": "USA" },
],
"types": ["locality", "political", "geocode"],
},
{
"description": "Paris, Brant, ON, Canada",
"matched_substrings": [{ "length": 5, "offset": 0 }],
"place_id": "ChIJsamfQbVtLIgR-X18G75Hyi0",
"reference": "ChIJsamfQbVtLIgR-X18G75Hyi0",
"structured_formatting":
{
"main_text": "Paris",
"main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
"secondary_text": "Brant, ON, Canada",
},
"terms":
[
{ "offset": 0, "value": "Paris" },
{ "offset": 7, "value": "Brant" },
{ "offset": 14, "value": "ON" },
{ "offset": 18, "value": "Canada" },
],
"types": ["neighborhood", "political", "geocode"],
},
{
"description": "Paris, KY, USA",
"matched_substrings": [{ "length": 5, "offset": 0 }],
"place_id": "ChIJsU7_xMfKQ4gReI89RJn0-RQ",
"reference": "ChIJsU7_xMfKQ4gReI89RJn0-RQ",
"structured_formatting":
{
"main_text": "Paris",
"main_text_matched_substrings": [{ "length": 5, "offset": 0 }],
"secondary_text": "KY, USA",
},
"terms":
[
{ "offset": 0, "value": "Paris" },
{ "offset": 7, "value": "KY" },
{ "offset": 11, "value": "USA" },
],
"types": ["locality", "political", "geocode"],
},
],
"status": "OK",
} XML
<AutocompletionResponse>
<status>OK</status>
<prediction>
<description>Paris, France</description>
<type>locality</type>
<type>political</type>
<type>geocode</type>
<reference>ChIJD7fiBh9u5kcRYJSMaMOCCwQ</reference>
<term>
<value>Paris</value>
<offset>0</offset>
</term>
<term>
<value>France</value>
<offset>7</offset>
</term>
<matched_substring>
<offset>0</offset>
<length>5</length>
</matched_substring>
<place_id>ChIJD7fiBh9u5kcRYJSMaMOCCwQ</place_id>
<structured_formatting>
<description>Paris</description>
<subdescription>France</subdescription>
<description_matched_substring>
<offset>0</offset>
<length>5</length>
</description_matched_substring>
</structured_formatting>
</prediction>
<prediction>
<description>Paris, TX, USA</description>
<type>locality</type>
<type>political</type>
<type>geocode</type>
<reference>ChIJmysnFgZYSoYRSfPTL2YJuck</reference>
<term>
<value>Paris</value>
<offset>0</offset>
</term>
<term>
<value>TX</value>
<offset>7</offset>
</term>
<term>
<value>USA</value>
<offset>11</offset>
</term>
<matched_substring>
<offset>0</offset>
<length>5</length>
</matched_substring>
<place_id>ChIJmysnFgZYSoYRSfPTL2YJuck</place_id>
<structured_formatting>
<description>Paris</description>
<subdescription>TX, USA</subdescription>
<description_matched_substring>
<offset>0</offset>
<length>5</length>
</description_matched_substring>
</structured_formatting>
</prediction>
<prediction>
<description>Paris, TN, USA</description>
<type>locality</type>
<type>political</type>
<type>geocode</type>
<reference>ChIJ4zHP-Sije4gRBDEsVxunOWg</reference>
<term>
<value>Paris</value>
<offset>0</offset>
</term>
<term>
<value>TN</value>
<offset>7</offset>
</term>
<term>
<value>USA</value>
<offset>11</offset>
</term>
<matched_substring>
<offset>0</offset>
<length>5</length>
</matched_substring>
<place_id>ChIJ4zHP-Sije4gRBDEsVxunOWg</place_id>
<structured_formatting>
<description>Paris</description>
<subdescription>TN, USA</subdescription>
<description_matched_substring>
<offset>0</offset>
<length>5</length>
</description_matched_substring>
</structured_formatting>
</prediction>
<prediction>
<description>Paris, Brant, ON, Canada</description>
<type>neighborhood</type>
<type>political</type>
<type>geocode</type>
<reference>ChIJsamfQbVtLIgR-X18G75Hyi0</reference>
<term>
<value>Paris</value>
<offset>0</offset>
</term>
<term>
<value>Brant</value>
<offset>7</offset>
</term>
<term>
<value>ON</value>
<offset>14</offset>
</term>
<term>
<value>Canada</value>
<offset>18</offset>
</term>
<matched_substring>
<offset>0</offset>
<length>5</length>
</matched_substring>
<place_id>ChIJsamfQbVtLIgR-X18G75Hyi0</place_id>
<structured_formatting>
<description>Paris</description>
<subdescription>Brant, ON, Canada</subdescription>
<description_matched_substring>
<offset>0</offset>
<length>5</length>
</description_matched_substring>
</structured_formatting>
</prediction>
<prediction>
<description>Paris, KY, USA</description>
<type>locality</type>
<type>political</type>
<type>geocode</type>
<reference>ChIJsU7_xMfKQ4gReI89RJn0-RQ</reference>
<term>
<value>Paris</value>
<offset>0</offset>
</term>
<term>
<value>KY</value>
<offset>7</offset>
</term>
<term>
<value>USA</value>
<offset>11</offset>
</term>
<matched_substring>
<offset>0</offset>
<length>5</length>
</matched_substring>
<place_id>ChIJsU7_xMfKQ4gReI89RJn0-RQ</place_id>
<structured_formatting>
<description>Paris</description>
<subdescription>KY, USA</subdescription>
<description_matched_substring>
<offset>0</offset>
<length>5</length>
</description_matched_substring>
</structured_formatting>
</prediction>
</AutocompletionResponse> PlacesAutocompleteResponse Field Required Type Description predictions required Array<PlaceAutocompletePrediction>
Contains an array of predictions.
See PlaceAutocompletePrediction for more information.
status required PlacesAutocompleteStatus
Contains the status of the request, and may contain debugging information to help you track down why the request failed.
See PlacesAutocompleteStatus for more information.
error_message optional string
When the service returns a status code other than OK<, there may be an additional error_message field within the response object. This field contains more detailed information about thereasons behind the given status code. This field is not always returned, and its content is subject to change.
info_messages optional Array<string>
When the service returns additional information about the request specification, there may be an additional info_messages field within the response object. This field is only returned for successful requests. It may not always be returned, and its content is subject to change.
Of particular interest within the results are the place_id elements, which can be used to request more specific details about the place using a separate query. See Place Details (Legacy) requests.
An XML response consists of a single <AutocompletionResponse> element with two types of child elements:
<status> element contains metadata on the request. See Status Codes below.<prediction> elements, each containing information about a single place. See Place Autocomplete (Legacy) Results for information about these results. The Places API returns up to 5 results.We recommend that you use json as the preferred output flag unless your application requires xml for some reason. Processing XML trees requires some care, so that you reference proper nodes and elements. See Processing XML with XPath for help processing XML.
street_number address component may not be present in Place Details (Legacy) responses for place IDs in some autocomplete predictions. This typically happens when the address cannot be interpolated for a place. In these cases, the prediction's types array will contain "route". For autocomplete predictions with a number in the description (input query is matched), the Place Details (Legacy) response for the place ID contains the street number only if the types array for the prediction contains at least one of:
Status codes returned by service.
OK indicating the API request was successful.ZERO_RESULTS indicating that the search was successful but returned no results. This may occur if the search was passed a bounds in a remote location.INVALID_REQUEST indicating the API request was malformed, generally due to the missing input parameter.OVER_QUERY_LIMIT indicating any of the following:
REQUEST_DENIED indicating that your request was denied, generally because:
key parameter is invalid.UNKNOWN_ERROR indicating an unknown error.When the Places service returns JSON results from a search, it places them within a predictions array. Even if the service returns no results (such as if the location is remote) it still returns an empty predictions array. XML responses consist of zero or more <prediction> elements.
description required string
Contains the human-readable name for the returned result. For establishment results, this is usually the business name. This content is meant to be read as-is. Do not programmatically parse the formatted address.
matched_substrings required Array<PlaceAutocompleteMatchedSubstring>
A list of substrings that describe the location of the entered term in the prediction result text, so that the term can be highlighted if desired.
See PlaceAutocompleteMatchedSubstring for more information.
structured_formatting required PlaceAutocompleteStructuredFormat
Provides pre-formatted text that can be shown in your autocomplete results. This content is meant to be read as-is. Do not programmatically parse the formatted address.
See PlaceAutocompleteStructuredFormat for more information.
terms required Array<PlaceAutocompleteTerm>
Contains an array of terms identifying each section of the returned description (a section of the description is generally terminated with a comma). Each entry in the array has a value field, containing the text of the term, and an offset field, defining the start position of this term in the description, measured in Unicode characters.
See PlaceAutocompleteTerm for more information.
distance_meters optional integer
The straight-line distance in meters from the origin. This field is only returned for requests made with an origin.
place_id optional string
A textual identifier that uniquely identifies a place. To retrieve information about the place, pass this identifier in the placeId field of a Places API request. For more information about place IDs, see the Place IDs overview.
reference optional string reference is deprecated.
See place_id.
types optional Array<string>
Contains an array of types that apply to this place. For example: [ "political", "locality" ] or [ "establishment", "geocode", "beauty_salon" ]. The array can contain multiple values. Learn more about Place types.
length required number
Length of the matched substring in the prediction result text.
offset required number
Start location of the matched substring in the prediction result text.
PlaceAutocompleteStructuredFormat Field Required Type Descriptionmain_text required string
Contains the main text of a prediction, usually the name of the place.
main_text_matched_substrings required Array<PlaceAutocompleteMatchedSubstring>
Contains an array with offset value and length. These describe the location of the entered term in the prediction result text, so that the term can be highlighted if desired.
See PlaceAutocompleteMatchedSubstring for more information.
secondary_text optional string
Contains the secondary text of a prediction, usually the location of the place.
secondary_text_matched_substrings optional Array<PlaceAutocompleteMatchedSubstring>
Contains an array with offset value and length. These describe the location of the entered term in the prediction result text, so that the term can be highlighted if desired.
See PlaceAutocompleteMatchedSubstring for more information.
PlaceAutocompleteTerm Field Required Type Descriptionoffset required number
Defines the start position of this term in the description, measured in Unicode characters
value required string
The text of the term.
Place Autocomplete (Legacy) optimizationThis section describes best practices to help you make the most of the Place Autocomplete (Legacy) service.
Here are some general guidelines:
To optimize the cost of using the Place Autocomplete (Legacy) service, use field masks in Place Details (Legacy) and Place Autocomplete (Legacy) widgets to return only the place data fields you need.
Advanced cost optimizationConsider programmatic implementation of Place Autocomplete (Legacy) in order to access Per Request pricing and request Geocoding API results about the selected place instead of Place Details (Legacy). Per Request pricing paired with Geocoding API is more cost-effective than Per Session (session-based) pricing if both of the following conditions are met:
For help selecting the Place Autocomplete (Legacy) implementation that fits your needs, select the tab that corresponds to your answer to the following question.
Does your application require any information other than the address and latitude/longitude of the selected prediction?
Yes, needs more detailsUse session-based Place Autocomplete (Legacy) with Place Details (Legacy).
Since your application requires Place Details (Legacy) such as the place name, business status, or opening hours, your implementation of Place Autocomplete (Legacy) should use a session token (programmatically or built into the JavaScript, Android, or iOS widgets). per session plus applicable Places Data SKUs depending on which place data fields you request.1
Widget implementation
Session management is automatically built into the JavaScript, Android, or iOS widgets. This includes both the Place Autocomplete (Legacy) requests and the Place Details (Legacy) request on the selected prediction. Be sure to specify the fields parameter in order to ensure you are only requesting the place data fields you need.
Programmatic implementation
Use a session token with your Place Autocomplete (Legacy) requests. When requesting Place Details (Legacy) about the selected prediction, include the following parameters:
fields parameter specifying the place data fields you needGeocoding API could be a more cost-effective option than Place Details (Legacy) for your application, depending on the performance of your Place Autocomplete (Legacy) usage. Every application's Place Autocomplete (Legacy) efficiency varies depending on what users are entering, where the application is being used, and whether performance optimization best practices have been implemented.
In order to answer the following question, analyze how many characters a user types on average before selecting a Place Autocomplete (Legacy) prediction in your application.
Do your users select a Place Autocomplete (Legacy) prediction in four or fewer requests, on average?
YesImplement Place Autocomplete (Legacy) programmatically without session tokens and call Geocoding API on the selected place prediction.
Geocoding API delivers addresses and latitude/longitude coordinates. Making four Place Autocomplete (Legacy) - Per Request requests plus a Geocoding API call about the selected place prediction is less than the Per Session Place Autocomplete (Legacy) cost per session.1
Consider employing performance best practices to help your users get the prediction they're looking for in even fewer characters.
NoUse session-based Place Autocomplete (Legacy) with Place Details (Legacy).
Since the average number of requests you expect to make before a user selects a Place Autocomplete (Legacy) prediction exceeds the cost of Per Session pricing, your implementation of Place Autocomplete (Legacy) should use a session token for both the Place Autocomplete (Legacy) requests and the associated Place Details (Legacy) request per session.1
Widget implementation
Session management is automatically built into the JavaScript, Android, or iOS widgets. This includes both the Place Autocomplete (Legacy) requests and the Place Details (Legacy) request on the selected prediction. Be sure to specify the fields parameter in order to ensure you are only requesting Basic Data fields.
Programmatic implementation
Use a session token with your Place Autocomplete (Legacy) requests. When requesting Place Details (Legacy) about the selected prediction, include the following parameters:
fields parameter specifying Basic Data fields such as address and geometryConsider delaying Place Autocomplete (Legacy) requests
You can employ strategies such as delaying a Place Autocomplete (Legacy) request until the user has typed in the first three or four characters so that your application makes fewer requests. For example, making Place Autocomplete (Legacy) requests for each character after the user has typed the third character means that if the user types seven characters then selects a prediction for which you make one Geocoding API request, the total cost would be for 4 Place Autocomplete (Legacy) Per Request + Geocoding.1
If delaying requests can get your average programmatic request below four, you can follow the guidance for performant Place Autocomplete (Legacy) with Geocoding API implementation. Note that delaying requests can be perceived as latency by the user who might be expecting to see predictions with every new keystroke.
Consider employing performance best practices to help your users get the prediction they're looking for in fewer characters.
Performance best practicesThe following guidelines describe ways to optimize Place Autocomplete (Legacy) performance:
Bias results to a specified area by passing a location parameter and a radius parameter. This instructs Place Autocomplete (Legacy) to prefer showing results within the defined area. Results outside of the defined area may still be displayed. You can use the components parameter to filter results to show only those places within a specified country.
radius is not provided, the location parameter is ignored.
Tip: Establishment results generally don't rank highly enough to show in results when the search area is large. If you want establishments to appear in mixed establishment/geocode results, you can specify a smaller radius. Alternatively, use types=establishment to restrict results to establishments only.
Restrict results to a specified area by passing a locationrestriction parameter.
You may also restrict results to the region defined by location and a radius parameter, by adding the strictbounds parameter. This instructs Place Autocomplete (Legacy) to return only results within that region.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-14 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4