Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services. You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.
New Users:
To use Google Maps Platform, you need a project with a billing account and at least one Google Maps Platform API or SDK enabled. Visit Get Started with Google Maps Platform for full instructions or click the button below for guided setup.
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, the Places SDK for iOS, and the Places Library, Maps JavaScript API.
The Places API is a service that returns information about places using HTTP requests. Places are defined within this API as establishments, geographic locations, or prominent points of interest.
Introducing the API
The following place requests are available:
- Place Search returns a list of places based on a user's location or search string.
- Place Details returns more detailed information about a specific place, including user reviews.
- Place Photos provides access to the millions of place-related photos stored in Google's Place database.
- Place Autocomplete automatically fills in the name and/or address of a place as users type.
- Query Autocomplete provides a query prediction service for text-based geographic searches, returning suggested queries as users type.
Each of the services is accessed as an HTTP request, and returns either an JSON or XML response. All requests to a Places service must use the https:// protocol, and include an API key.
The Places API uses a place ID to uniquely identify a place. For details about the format and usage of this identifier across the Places API and other APIs, see the Place IDs documentation.
Policies and Terms
All applications that use the Places API or Place Autocomplete service must adhere to the requirements described in the Places API Policies and the Google Maps Platform Terms of Service. The Places API and Google Place Autocomplete share the usage quota as described in the Places API Usage and Billing documentation.
For quota and pricing information for the Places API and Place Autocomplete service, see the Places API Usage and Billing documentation.
Place IDs uniquely identify a place in the Google Places database and on Google Maps.
Find the ID of a particular place
Are you looking for the place ID of a specific place? Use the place ID finder below to search for a place and get its ID:
Alternatively, you can view the place ID finder with its code in the Maps JavaScript API documentation.
Overview
A place ID is a textual identifier that uniquely identifies a place. The length of the identifier may vary. Examples:
Place IDs are available for most locations, including businesses, landmarks, parks, and intersections.
You can use the same place ID across the Places API and a number of Google Maps Platform APIs. For example, you can use the same place ID to reference a place in the Places API, the Maps JavaScript API, the Maps Geocoding API, the Maps Embed API and the Roads API.
Retrieve place details using the place ID
Place IDs are exempt from the caching restrictions stated in Section 3.2.4(a) of the Google Maps Platform Terms of Service. Once you've identified the place ID for a place, you may reuse that value the next time you look up that place. For more information, see Save place IDs for later use below.
A common way of using place IDs is to search for a place (using the Places API or the Places library in the Maps JavaScript API, for example) then use the returned place ID to retrieve place details. You can store the place ID and use it to retrieve the same place details later. Read about saving place IDs below.
Example using the Places library in the Maps JavaScript API
To use a place ID in your JavaScript app, you must first find the ID, which is available in the PlaceResult returned by a Place Search, or by getPlace() in the Place Autocomplete service. Then you can use the place ID to look up place details.
Save place IDs for later use
Place IDs are exempt from the caching restrictions stated in Section 3.2.4(a) of the Google Maps Platform Terms of Service. You can therefore store place ID values for later use.
You may occasionally receive a NOT_FOUND status code when you use a saved place ID. Best practice is to refresh your stored place IDs periodically. You can refresh Place IDs free of charge, by making a Place Details request, specifying only the ID field in the fields parameter. This will trigger the Places Details - ID Refresh SKU. However, this request might also return NOT_FOUND status code. One strategy is to store the original request that returned each place ID. If a place ID becomes invalid, you can re-issue that request to get fresh results. These results may or may not include the original place. The request is chargeable.
Google Slides
A place ID may become obsolete if a business closes or moves to a new location.
Place IDs may change due to large-scale updates on the Google Maps database. In such cases, a place may receive a new place ID, and the old ID returns a NOT_FOUND response.
In particular, some types of place IDs may sometimes cause a NOT_FOUND response, or the API may return a different place ID in the response. These place ID types include:
- Street addresses that do not exist in Google Maps as precise addresses, but are inferred from a range of addresses.
- Segments of a long route, where the request also specifies a city or locality.
- Intersections.
- Places with an address component of type
subpremise.
Purble Place Google Docs Free
These IDs often take the form of a long string. Example: