We’ve been using Postman to get implicit-grant access tokens for Auth0 with our custom domain url up until today, when we get the following error “You should not be hitting this endpoint”. The endpoint we’re hitting is /authorize?audience= This is what Postman shows: [40%20PM]

New information: We found that Postman will still be able to access /authorize and get us a token via Google Oauth (which is what we were doing previously via the login page) if we add these parameters to /authorize: &connection=google-oauth2&prompt=select_account

Implicit Oauth token not working anymore with custom auth0 domain

Get Help

hantonr August 7, 2018, 12:22am 2

We assume this is somehow related to the newly deprecated APIs.

Topic		Replies	Views
Login via API with Custom Domains - invalid domain x for clientId y Get Help token , auth0 , password , custom-domain , access-token	2	4019	March 25, 2021
Custom domain with default login page has end point error Get Help auth0 , custom-domain	3	4989	August 17, 2018
Test API access tokens don't use custom domain Get Help custom-domain , access-token	1	3059	May 7, 2021
Use Custom Domain instead of Canonical Domain in Auth0 Dashboard API Test page Get Help auth0 , access_token , authentication , custom-domain	3	43	August 31, 2026
Custom Domain + Google OAuth Login + Development Environment not working Get Help development , custom-domain , oauth2 , universal-login	2	3285	April 28, 2022

Implicit Oauth token not working anymore with custom auth0 domain

Related topics