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

**URL:** https://ask.openrouteservice.org/t/deprecating-api-openrouteservice-org-in-favour-of-api-heigit-org/7912
**Category:** Announcements
**Created:** [April 28, 2026, 1:37pm UTC](https://ask.openrouteservice.org/t/deprecating-api-openrouteservice-org-in-favour-of-api-heigit-org/7912 "2026-04-28T13:37:05Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jschnell](https://ask.openrouteservice.org/user_avatar/ask.openrouteservice.org/jschnell/32/971_2.png) [@jschnell](https://ask.openrouteservice.org/u/jschnell)
#### Post date: [May 13, 2026, 1:12pm UTC](https://ask.openrouteservice.org/t/deprecating-api-openrouteservice-org-in-favour-of-api-heigit-org/7912/2 "2026-05-13T13:12:36Z")

</div>

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](https://ask.openrouteservice.org/t/cors-headers-missing-on-api-heigit-org-browser-requests-blocked-from-browser-based-client/7926/) has a bit more details

---

_[View the full topic](https://ask.openrouteservice.org/t/deprecating-api-openrouteservice-org-in-favour-of-api-heigit-org/7912)._