On Monday 5 October 2026, Google marks three well-known Google Maps Platform services as End of Sale: the legacy Places API, the legacy Directions API and the legacy Distance Matrix API. The short version: if your application already uses them, nothing changes. If you are starting something new, you will build on Places API (New) and the Routes API.
What is changing?
These three APIs have carried Legacy status since 1 March 2025. End of Sale is the next step. From 5 October, new customers and newly created Google Cloud projects can no longer enable the legacy versions. They are directed to Places API (New) and the Routes API instead.
What does this mean for existing integrations?
Nothing, for now. Existing accounts and active projects keep full, uninterrupted access to the legacy APIs. There is no forced migration and no deadline. Google has also confirmed that it will give at least 12 months’ notice before any legacy service is eventually shut down.
There is one situation to keep in mind. If you create a new project ID and that project still needs a legacy API, you can no longer simply switch it on. You can request an exception through Google Maps Platform Support. If you see a LegacyApiNotActivatedMapError, often triggered by an older plugin or app on a new project, this is the reason. Google explains the error and the exception on its Legacy products page.
Why migrate anyway?
Legacy services are feature frozen. All new functionality lands in the new APIs. Places API (New) and the Routes API offer improved performance, richer data and better cost control, for example by requesting only the fields you actually need. So while there is no rush, the sooner you plan your migration, the sooner you benefit, and the less you depend on an exception process for future projects.
Quick answers
- Does my current application stop working? No. Existing projects keep running on the legacy APIs.
- Is there a migration deadline? No. You decide when you are ready.
- I am starting a new project. Can I still use the legacy APIs? By default, no. Build on Places API (New) and the Routes API, or request an exception through Support if you really need the legacy version.
- Where can I find migration guides? Google lists them per service on its Legacy products page.
How Localyse can help
Not sure which of your applications still use the legacy APIs, or what a migration would mean for your costs? Localyse can map out where you stand, estimate the impact and guide your team through the switch, at your own pace. Contact us and we will gladly think along.
