/authorize and /token endpoints in Sandbox

Authentication API
1

Hi @budd.renaud

I have observed two different host url’s - “https://auth.dev.mitel.io/authorize” and “https://authentication.dev.api.mitel.io/2017-09-01/authorize” . The first url lands to to the login UI from browser and I was expecting the latter to do the same or redirect to login page to maintain consistency since it is also used for other API calls such as /token but it only works with POST request.

This means to maintain two different base URL’s instead of one. I want to know if this will be the same for production as well ?

2

The first URL is for the authentication web portal, the second is for the authentication API, as you’ve identified. While the web portal does use the API, they are entirely separate entities. This will be the same as production, where the URLs are:

https://auth.mitel.io/authorize
https://authentication.api.mitel.io/2017-09-01/authorize