Places API (New) quick reference

Places API (New) is a web service that returns JSON location data about establishments, geographic locations, and points of interest. It supports Text Search (New), Nearby Search (New), Autocomplete (New), Place Details (New), and Place Photos (New).

Places API (New): key facts

  • Product: Places API (New)
  • Also known as: Places API
  • Category: Places
  • Platform: Web service (REST)
  • Runs on: Server (backend code)
  • Launch stage: GA
  • Lifecycle: Active
  • Overview: Places API (New) overview
  • Regional availability: Global. Projects with EEA billing addresses use the Google Maps Platform EEA Terms of Service (effective 8 July 2025), where Places API content other than latitude, longitude, and place IDs can't be used with any map except through the Places UI Kit. AI-powered place, review, and area summaries are available only in supported languages and regions.

Places API (New): when to use it

Use Places API (New) when:

  • You need to search for places from a server with a text query (Text Search (New)) or around a location (Nearby Search (New)).
  • You need type-ahead place or query predictions from a backend through Autocomplete (New).
  • You have a place ID and need details such as address, phone number, rating, reviews, or photos.
  • You need AI-powered place, review, or area summaries for a place.

Don't use Places API (New) when:

Places API (New): setup

Official Places API (New) packages:

  • npm: @googlemaps/places
  • pypi: google-maps-places
  • go: cloud.google.com/go/maps

Places API (New): common mistakes

  • Problem: Place Details (New), Nearby Search (New), and Text Search (New) have no default list of returned fields; requests without a field mask return an error. Fix: Pass a response field mask with the fields or $fields parameter, or the X-Goog-FieldMask header. See /maps/documentation/places/web-service/choose-fields.
  • Problem: If the Autocomplete (New) session token is omitted or reused after a session concludes, each request is billed separately as SKU: Autocomplete Requests. Fix: Generate a fresh session token (UUID v4 recommended) for each session and end it with a Place Details (New) or Address Validation request. See /maps/documentation/places/web-service/place-session-tokens.
  • Problem: Existing or AI-generated code that calls Places API (Legacy) or the Maps JavaScript API PlacesService on a project without the legacy API enabled fails with LegacyApiNotActivatedMapError. Fix: Migrate the calls to Places API (New) and include the required field mask. See /maps/legacy#LegacyApiNotActivatedMapError.
  • Problem: Stored place IDs can become obsolete; Place Details (New) then returns NOT_FOUND (HTTP 404), and malformed or truncated IDs return HTTP 400 INVALID_ARGUMENT. Fix: Refresh stored place IDs older than 12 months with a Place Details (New) request that asks only for the id field (no charge). See /maps/documentation/places/web-service/place-id#refresh-id.

What you can do with Places API (New)

See the guides linked below for each task, or compare across products in the Capabilities Explorer.

Places API (New): Generative AI

Places API (New): Places