In February, we launched the Preview phase of Autocomplete in Places API, offering seamless integration with Address Validation, new outcome-based pricing, and support for expanded place types from the new Places API. Today, we’re pleased to share that the next generation of Autocomplete is now generally available via Places API, Maps JavaScript API and Places SDK for Android and iOS.
New outcome-based pricing
We’ve updated our pricing for the next generation of Autocomplete to be based on session outcomes that reflect how your users utilize Autocomplete, and to better align with the value you get from it:
-
One outcome is your user doesn’t complete their session—e.g., they enter a few characters in your search box and then close their browser. In this scenario, you will be billed the Autocomplete Requests SKU for the requests (characters entered) your user makes, up to 12 requests.
-
A second outcome is your user does complete their session by selecting an address from the Autocomplete suggestions. In this instance, you will be billed the Autocomplete with Place Details (Location Only) SKU, which provides additional location details about the place, such as city, state and postal code.
-
A third outcome is your user completes their session, and then submits and validates their address to have an item shipped to them. In this scenario, you will be billed the Autocomplete with Address Validation Preferred SKU, designed for e-commerce use cases.
In addition to these scenarios, we also now offer an Autocomplete with Place Details Preferred SKU, for when you want to help users not only find places, but discover more about those places with rich place details such as opening hours, user ratings and reviews, and price levels.
The new Places API is now generally available on all platforms
In addition to offering many new features, the new Places API is now close to parity with the previous version, with the exception of the Autocomplete widget. It’s generally available today on all platforms, giving you modernized APIs and SDKs to help you focus on building and launching great products on whatever surfaces you choose.
It offers new features in Text Search, Place Details and Photos, Nearby Search and Autocomplete, to make it easier for you to surface helpful information about the world in the products you build. The new features include improved text search, nearly twice the number of supported place types since the previous version, and additional accessibility information for places.
New use cases for accessibility and travel
Together the new Autocomplete and Place Details enable additional use cases. For example, with additional accessibility information, you can help wheelchair users navigate with ease by providing wheelchair-accessible seating, restrooms, and parking options. Using new place information for EV charging stations, and fuel and parking options, you can also help drivers further optimize their travel plans by showing gas stations with specific fuel options, available parking or finding the ideal EV charging stations - right down to real-time availability, connector type, and max charging speed.
In addition, new features will be available on the new Places, including the ability to provide AI-powered place and area summaries, with new Gemini model capabilities for the Places API.
How to get started
When you get started with the next generation Autocomplete , ensure "Places API (New)” is enabled on your Google Cloud project. To learn more about the new Places API, check out our webpage and documentation, and use our pricing calculator to explore pricing at different usage levels.
