Migration overview

The Places API (New) provides improved performance and a new pricing model, making it worthwhile to update apps that use Places API. For more details on comparing features, see Choose your API.

Use this guide to understand key differences in Places API (New) compared to Places API, along with how to handle necessary changes.

Billing best practices for migration

This guidance applies if your API usage is high enough to move into second-tier pricing. When migrating to a newer version of an API, you're also being billed for a different SKU. To avoid increased costs during the month of your transition, we recommend switching to the new APIs in production as close to the beginning of the month as possible. This will ensure that you reach the most cost-effective monthly pricing tiers during the migration month. For information about pricing tiers, see the pricing page and the pricing FAQ.

Enable Places API (New)

To use the features of Places API (New), you must first enable Places API (New) in your Google Cloud project. For more information, see Set up your Google Cloud project.

You then must ensure that you have added Places API (New) to the API key used by your app. For more information, see Use API Keys.

General changes

Some general changes that apply to multiple APIs include:

API-specific changes

This section includes the following migration guides for each API: