Migrate a Google Maps Places integration from the Legacy Places API to Places API (New)

domain: developers.google.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Confirm Places API, the JS Places Service, and the Places SDKs for Android/iOS all moved to Legacy status on March 1, 2025 per developers.google.com/maps/legacy
  2. Understand "Legacy" means feature-frozen but still fully supported — only new Cloud projects are blocked from enabling it, existing usage keeps working
  3. Note Google has not published a decommission date yet, but its terms require at least 12 months notice before any actual turn-down
  4. Rebuild calls against the new base host https://places.googleapis.com/v1/ using the new named methods: Text Search (New), Nearby Search (New), Place Details (New), Place Photos (New), and Autocomplete (New)
  5. Add explicit field masks to every Places API (New) request, since omitted field masks return empty or error responses (unlike the legacy API's default field behavior)

Known gotchas

Related routes

Migrate a legacy Google Directions API integration to the Routes API computeRoutes method with an explicit field mask
developers.google.com · 5 steps · unrated
Migrate an existing ShipStation V1 API integration to the ShipStation API V2
docs.shipstation.com · 5 steps · unrated
Migrate a DocuSign integration from the legacy SOAP API to the REST eSignature API
developers.docusign.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans