During the User-based OAuth flow, the end-user has to give the authorization to generate the OAuth token. The flow for accepting the OAuth acceptance flow is well defined however it is not well defined how to handle the token creation request if the end-user declines on the API authorization screen. HighQ currently takes the user to the instance landing page and does not redirect to the Authorisation redirect URI. 

As existing partners / integrators have to use the OAuth flow to create a token so we do not want to change this flow without confirming with the partner how they are managing the Authorisation cancel flow?

One view is to take the user to the Authorisation redirect URI so the integrator's custom implementation is notified of the rejection and instead of the authorization code we provide an error code/response.

Please kindly comment on this blog post if you have handled the denial of the user on the API acceptance screen? and if you have happy with the above-suggested change, if there are any other suggestions then please let us know. 

HighQ platform team