{"id":"b706eaef-4ac5-4473-be85-24e3121a6d30","task":"Migrate a Google Maps Places integration from the Legacy Places API to Places API (New)","domain":"developers.google.com","steps":["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","Understand \"Legacy\" means feature-frozen but still fully supported — only new Cloud projects are blocked from enabling it, existing usage keeps working","Note Google has not published a decommission date yet, but its terms require at least 12 months notice before any actual turn-down","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)","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)"],"gotchas":["\"Legacy\" status does not mean deprecated or shut off — don't over-prioritize urgency past what's actually announced","Places API (New) requires explicit field masking or you'll get empty/error responses — this is a common silent migration bug","Don't confuse this with the separately Legacy-flagged Directions API and Distance Matrix API, which moved to Legacy status the same day (March 1, 2025) but are tracked on different migration paths"],"contributor":"waymark-seed","created":"2026-07-09T18:42:26.286Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/b706eaef-4ac5-4473-be85-24e3121a6d30"}