New Routes api key does not work with Directions api

[benderlidze]

Description

The problem is that I created a new Google Maps account and a new API key, but there is no Directions API. They say you should use the Routes API. However, when I use the new API key with the Routes API enabled, I get
MapsRequestError: DIRECTIONS_ROUTE: REQUEST_DENIED: There was an issue performing a Directions request.
Uncaught (in promise) MapsRequestError: DIRECTIONS_ROUTE: REQUEST_DENIED: The webpage is not allowed to use the directions service.

When I use an old API key from 5 years ago with the Directions API enabled, it works fine.

Steps to Reproduce

Create new google account and Reoutes api.

Environment

• Library version:
• Google maps version: weekly
• Browser and Version:
• OS:

Logs

[usefulthink]

This doesn't have anything to do with the react-library, but let's see if I can help you anyway...

Have you checked that not only the Routes API is enabled for your GCP project, but also the Directions API is enabled for the Maps API Key (https://console.cloud.google.com/google/maps-apis/credentials)?

[benderlidze]

@usefulthink It looks like the Directions API no longer exists. There is only the Routes API.
https://developers.google.com/maps/documentation/routes/migrate-routes

[usefulthink]

After a bit of searching, I found the answer: the old version of the Places API, the Directions API and the Distance Matrix API as well as their classes in the Maps JavaScript API have been declared "legacy", which means they can no longer be enabled for new projects. Most annoying is that they did this without having a replacement for the DirectionsService or DirectionsRenderer available (yet). Sounds like we need to get to work updating all relevant examples here...

A bit more info can be found here: https://developers.google.com/maps/legacy

[sanderquirynen]

I seem to have the same issue with the new Places API.

I get "This API project is not authorized to use this API. Places API error: ApiNotActivatedMapError", while having "Places API (new)" enabled and no API restrictions on my API key.

Geocoding works with the same API key.

[usefulthink]

yeah, with the places API things are slightly different. At least there are new parts of the Maps JavaScript API to use them with. PlacesService, Autocomplete, and SearchBox from google.maps.places are all using the legacy Places API, and the Place class and AutocompleteSuggestion are using the new APIs.

[sahibjotsaggu]

@usefulthink do you know how we can enable the legacy Places API? I can't find that on the "APIs & Services" page.

[usefulthink]

@sahibjotsaggu It might still be possible using this direct link: https://console.cloud.google.com/apis/library/places-backend.googleapis.com

[zerdotre]

@sahibjotsaggu It might still be possible using this direct link: https://console.cloud.google.com/apis/library/places-backend.googleapis.com

This worked, thanks! Where can one find a direct link to the legacy directions and distancematric apis?

[usefulthink]

Should be those three. But this might be only temporary, since the documentation on the legacy features says those APIs can no longer be activated for new projects.

• Places API (Legacy)
• Directions API (Legacy)
• Distance Matrix API (Legacy)

[zerdotre]

thank you, found them. indeed just eplacing places with directions or distance-matrix in the url. Yeah they cant be found in the library anymore but with direct links they can be enabled. Fortunately.

…

On Mon, 24 Mar 2025 at 20:45, Martin Schuhfuss ***@***.***> wrote: Should be those three. But this might be only temporary, since the documentation on the legacy features <https://developers.google.com/maps/legacy> says those APIs can no longer be activated for new projects. - Places API (Legacy) <https://console.cloud.google.com/apis/library/places-backend.googleapis.com> - Directions API (Legacy) <https://console.cloud.google.com/apis/library/directions-backend.googleapis.com> - Distance Matrix API (Legacy) <https://console.cloud.google.com/apis/library/distance-matrix-backend.googleapis.com> — Reply to this email directly, view it on GitHub <#712 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3B6HAJVM36J2KRQIASGCQT2WBADFAVCNFSM6AAAAABY4UGITWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBYHE2DQMRYGQ> . You are receiving this because you commented.Message ID: ***@***.***> [image: usefulthink]*usefulthink* left a comment (visgl/react-google-maps#712) <#712 (comment)> Should be those three. But this might be only temporary, since the documentation on the legacy features <https://developers.google.com/maps/legacy> says those APIs can no longer be activated for new projects. - Places API (Legacy) <https://console.cloud.google.com/apis/library/places-backend.googleapis.com> - Directions API (Legacy) <https://console.cloud.google.com/apis/library/directions-backend.googleapis.com> - Distance Matrix API (Legacy) <https://console.cloud.google.com/apis/library/distance-matrix-backend.googleapis.com> — Reply to this email directly, view it on GitHub <#712 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3B6HAJVM36J2KRQIASGCQT2WBADFAVCNFSM6AAAAABY4UGITWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBYHE2DQMRYGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[usefulthink]

I've created a new example showing how to use render results from the Routes-API using a simple Polyline component: https://visgl.github.io/react-google-maps/examples/routes-api