403 "Invalid API key or access to this API has been disallowed" despite valid key and usage under limit

openrouteservice
1

Hi,

I’m getting a 403 Forbidden error with the message:

Invalid API key or access to this API has been disallowed

This happens both when calling the API directly from my own application and when testing the exact same key in the API Playground on the ORS dashboard — so it doesn’t seem to be a client-side/integration issue.

Details:

  • API key: valid (visible and active in my dashboard) — happy to share the key ID (not the secret) if a maintainer needs it to look up my account
  • Usage: well under my plan’s request/rate limits — checked in the dashboard usage stats
  • Endpoint(s) affected: [https://api.openrouteservice.org/v2/directions/driving-car\]
2

Dear gsdp,

This is due to an outdated API address.
Please check this announcement for further details:

Cheers,
Matthias

3

Hi Matthias,

Found it — thanks for your patience. The root cause was the path structure actually.

I had originally copied the endpoint URL directly from the ORS Playground, which shows:

https://api.heigit.org/heigit/openrouteservice/v2

This path doesn’t actually exist (extra heigit/ segment) and returns a 404/403 — which is why testing directly in the Playground was also failing, not just my own client.

Per the migration announcement, the correct path is:

https://api.heigit.org/openrouteservice/v2/directions/driving-car

Using this corrected path with a valid key resolves the issue on my end.

Might be worth flagging to the team as a bug in the Playground’s displayed/generated URL, since it would affect anyone else testing there during the migration.

Thanks again for the help!

4

Hi @gsdp ,

you are right.

This is the actually correct one:

https://api.heigit.org/openrouteservice/v2/directions/driving-car

The playground is now fixed and shows the correct url.

Best

Julian

1 Like