Introduction

The Places API lets you search for and retrieve information for a variety ofplace types using a text string or by proximity. Places API (Legacy) is the legacyversion ofPlaces API (New).

The following table lists the corresponding versions of both APIs. Use thisguide to understand the key differences between the two and migrate toPlaces API (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 Photos (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 theserviceinfrastructure on Google Cloud. This implementation brings with it a more secure and trustedplatform with enhanced security options likeOAuth. This standard APIdesign brings a level of consistency across the APIs that improve the efficiencyof development with Places API (New).

Improved performance

Places API (New) provides improved performance, making it worthwhile toreplace apps that use the existing Places API.

Simplified pricing

Pricing is simplified with Places API (New) so that you only pay for thedata you use. Simplified pricing is implemented using afieldmask.

With Place Details (New), Nearby Search (New), andText Search (New) you use the field mask to control the list of fields toreturn in the response. You are then only billed for the data requested. Usingfield masking is a good design practice to ensure that you don't requestunnecessary data, which helps to avoid unnecessary processing time and billingcharges.

Consistent response data for a place

With the legacy APIs, the Place Details (Legacy), Nearby Search (Legacy), andText Search (Legacy) APIs returned different response data for a place.Places API (New) standardizes the response so these APIs all return thesame data for a place.

Expanded place types

The API response can now contain a place'sprimary type. Every place can havea single type value that is specified as the place's primary type, as listed inTable A.

The new API also includes several new types. You can use these new types, andthe existing types, in a search with Nearby Search (New)and Text Search (New). The new types are all included inTableA.

Dynamic place data

Places API (New) supports dynamic response data, such as the availabilityof an EV charging station or the latest fuel prices for a gas station. Use theseresponse fields to create dynamic user experiences.