Places API (Legacy) quick reference

Places API (Legacy) can no longer be enabled for new Google Cloud projects as of October 2026. Existing projects remain fully supported. For new features and improved performance, migrate to Places API (New).

Places API (Legacy): key facts

  • Product: Places API (Legacy)
  • Also known as: Places API (legacy web service), Places API web service (maps/api/place)
  • Category: Places
  • Platform: Web service (REST)
  • Runs on: Server (backend code)
  • Launch stage: GA
  • Lifecycle: Legacy
  • Replaced by: Places API (New)
  • Overview: Places API (Legacy) overview

Places API (Legacy): when to use it

Use Places API (Legacy) when:

  • You maintain an existing project that already has Places API (Legacy) enabled and calls maps.googleapis.com/maps/api/place endpoints.
  • You need existing Find Place, Nearby Search, Text Search, Details, Photos, or Autocomplete (Legacy) calls to keep working while you migrate.

Don't use Places API (Legacy) when:

  • You're starting a new Google Cloud project. As of October 2026, Places API (Legacy) can't be enabled for new projects. Use Places API (New) instead.
  • You need new features, OAuth authentication, or field masks on Nearby Search and Text Search so you pay only for the fields you request. Use Places API (New) instead.
  • You need Find Place (Legacy) or Query Autocomplete (Legacy) in new code. Text Search (New) and Autocomplete (New) replace them. Use Places API (New) instead.

Places API (Legacy): setup

Places API (Legacy): common mistakes

  • Problem: If a Place Details (Legacy) request omits the fields parameter or specifies no fields, the API returns all fields and bills you for all of them. Fix: Always set the fields parameter, or migrate to Place Details (New) with a field mask. See /maps/documentation/places/web-service/legacy/details.
  • Problem: Nearby Search (Legacy) and Text Search (Legacy) don't support specifying which fields to return. They always return a fixed set of fields (a subset of Place Details fields) and trigger the Basic Data, Contact Data, and Atmosphere Data SKUs. Fix: Migrate to Nearby Search (New) or Text Search (New) with a field mask, or use Find Place (Legacy) with the fields parameter to request and pay for only the fields you need. See /maps/billing-and-pricing/sku-details/legacy#places_nearby-search-legacy-pro-sku.
  • Problem: A photo_reference can't be cached and can expire, so stored references stop working. Fix: Get a fresh photo_reference from a Place Details, Find Place, Nearby Search, or Text Search response before you request a photo. See /maps/documentation/places/web-service/legacy/photos.
  • Problem: Calls to Places API (Legacy) from a project that doesn't have it enabled return REQUEST_DENIED with the error message "You're calling a legacy API, which is not enabled for your project..." (LegacyApiNotActivatedMapError). As of October 2026, Places API (Legacy) can't be enabled for new projects. Fix: Use Places API (New) for new projects and migrate existing apps. While you migrate, you can request short-term activation of the legacy API through the feedback form on the legacy page. See /maps/legacy#LegacyApiNotActivatedMapError.

Places API (Legacy): legacy and deprecated features

  • permanently_closed response field: Deprecated since 2020-05-26. Replacement: business_status field. See the migration guide.
  • reference response field: Deprecated since 2019-09-03. Replacement: place_id field. See the migration guide.
  • Nearby Search (Legacy) name request parameter: Deprecated. Replacement: keyword parameter. See the migration guide.