1
During Dashboard Uber configuration the privilege scopes are not displayed, but during authentication call to obtain the access token at least one scope is required.
The configuration screen always points out the need to contact Uber but has no direct channel for implementation support. How to proceed?
called route: https://login.uber.com/oauth/v2/token: POST
{
"client_id" => "#####",
"client_secret" => "#####",
"redirect_uri" => "https://webHook",
"grant_type" => "client_credentials",
"code" => "#####"
}
sponse:
{
"message":"invalid_scope"
}
NOTE: Even if you report any of the scopes presented in the Uber API, you don’t get a different return.
Your url is probably wrong, it should be something like:
https://login.uber.com/oauth/v2/authorize?client_id=<CLIENT_ID>&response_type=code&scope=profile&redirect_uri=<url de retorno>
– Guilherme Nascimento