The Places API lets you search for and retrieve information for a variety of place types using a text string or by proximity. Places API is the legacy version of Places API (New).
The following table lists the corresponding versions of both APIs. Use this guide to understand the key differences between the two and migrate to Places API (New).
| Places API (Legacy) | Places API (New) | Notes |
|---|---|---|
| Find Place (Legacy) | Text Search (New) | There is no new version of Find Place. Text Search (New) has replaced it. |
| Nearby Search (Legacy) | Nearby Search (New) | All requests using the legacy API that include a text query should use Text Search (New) because Nearby Search (New) does not support text input. |
| Text Search (Legacy) | Text Search (New) | |
| Place Details (Legacy) | Place Details (New) | |
| Place Photo (Legacy) | Place Photo (New) | |
| Place Autocomplete (Legacy) | Autocomplete (New) | |
| Query Autocomplete (Legacy) | Autocomplete (New) | Capabilities added to Autocomplete (New). |
Migrate to the new APIs
To migrate to the new APIs, see the following migration guides:
- Migrate to Nearby Search (New)
- Migrate to Text Search (New)
- Migrate to Place Details (New)
- Migrate to Place Photo (New)
- Migrate to Autocomplete (New)
Key features added to Places API (New)
This section covers key features added to Places API (New).
Implemented on the Google Cloud standard platform
Places API (New) is implemented on the service infrastructure on Google Cloud. This implementation brings with it a more secure and trusted platform with enhanced security options like OAuth. This standard API design brings a level of consistency across the APIs that improve the efficiency of development with Places API (New).
Improved performance
Places API (New) provides improved performance, making it worthwhile to replace apps that use the existing Places API.
Simplified pricing
Pricing is simplified with Places API (New) so that you only pay for the data you use. Simplified pricing is implemented using a field mask.
With Place Details (New), Nearby Search (New), and Text Search (New) you use the field mask to control the list of fields to return in the response. You are then only billed for the data requested. Using field masking is a good design practice to ensure that you don't request unnecessary data, which helps to avoid unnecessary processing time and billing charges.
Consistent response data for a place
With the existing APIs, the Place Details, Nearby Search, and Text Search APIs returned different response data for a place. Places API (New) standardizes the response so these APIs all return the same data for a place.
Expanded place types
The API response can now contain a place's primary type. Every place can have a single type value that is specified as the place's primary type, as listed in Table A.
The new API also includes several new types. You can use these new types, and the existing types, in a search with Nearby Search (New) and Text Search (New). The new types are all included in Table A.
Dynamic place data
Places API (New) supports dynamic response data, such as the availability of an EV charging station or the latest fuel prices for a gas station. Use these response fields to create dynamic user experiences.