Deprecating "api.openrouteservice.org" in favour of "api.heigit.org"

Announcements
1

Dear users,

as we are moving to a unified structure for all existing and future HeiGIT APIs, we are deprecating the URL api.openrouteservice.org in favour of api.heigit.org.

All users are encouraged to switch to api.heigit.org as described below.

This is only a deprecation of the URL, not a deprecation of the services accessible via api.openrouteservice.org - you will still be able to use all services as before, just with a different URL!

Timeline

  • Today: api.openrouteservice.org is officially deprecated.
    Access via api.openrouteservice.org will remain possible, but depending on usage, quota forapi.openrouteservice.org might be restricted to encourage the change to api.heigit.org.
  • August 24, 2026 : Shut-off api.openrouteservice.org

Required changes

Going forward, all HeiGIT APIs will adhere to the following structure:
api.heigit.org/<service name>/<API version>/

For the APIs accessible via api.openrouteservice.org, this means the following changes in the URLs used to access the API:

deprecated URL URL to be used
api.openrouteservice.org/v2/directions api.heigit.org/openrouteservice/v2/directions
api.openrouteservice.org/v2/isochrones api.heigit.org/openrouteservice/v2/isochrones
api.openrouteservice.org/v2/matrix api.heigit.org/openrouteservice/v2/matrix
api.openrouteservice.org/v2/snap api.heigit.org/openrouteservice/v2/snap
api.openrouteservice.org/v2/export api.heigit.org/openrouteservice/v2/export
api.openrouteservice.org/geocode api.heigit.org/pelias/v1
api.openrouteservice.org/elevation api.heigit.org/openelevationservice/v0
api.openrouteservice.org/optimization api.heigit.org/vroom/v0
api.openrouteservice.org/pois api.heigit.org/openpoiservice/v0/pois

Apart from that, everything else stays the same. Your API key is already set up to be able to access the new URLs and the quota reflected in your dashboard is also the one for api.heigit.org.

Other notes

  • The interactive API documentation will switch to using api.heigit.org in the coming weeks.
  • We have simplified the API quota structure. As before, you can find it on the HeiGIT Account Page.
  • If you come across api.openrouteservice.org somewhere, feel free to let us know :slight_smile:

Do not hesitate to contact us with all questions that may arise.

Best regards and happy routing,
the openrouteservice team

1 Like
2

Dear users,

Currently, access to api.heigit.org from a browser is not fully possible as intended.¹
This means that integrating the openrouteservice API into an external app is currently limited.

Unfortunately, this is due to a regression in an external depenency of our User Management stack.
We know that this is a pressing issues, but we will not be able to fix it this week.

We will update you here once a fix is in place.

Best regards,
the openrouteservice team

[1]: This thread has a bit more details

1 Like
CORS headers missing on api.heigit.org — browser requests blocked from browser-based client
3

Dear users,

CORS should now be handled correctly by the APIs running under api.heigit.org.

Please note tho following common pitfall when using CORS:

As specified in the MDN Web Docs, the Access-Control-Request-Headers should be a
sorted, unique, comma-separated and lowercase list. Any non-compliance with this will result in CORS errors.

Feel free to reach out if you are experiencing issues, but remember to include the full request that is giving you issues, ideally as a cURL-request. These can usually be taken from your browsers developer tools.

Best regards
the openrouteservice team