Hoping someone can help me understand why I’m receiving an “error”:“invalid_scope”,“error_description”:“scope(s) are invalid”, for Uber Direct authentication. Here is the documentation:
https://developer.uber.com/docs/deliveries/guides/authentication
Hello @bell.jeremy.robert, I’m actually having the same problem. Did you find a solution?
Thank you.
I am also having the same issue. I can get the token using production credentials but not testing credentials. Anyone know why? @alvarolo98 @bell.jeremy.robert
Did you set your Application in Uber Direct and not just “uber”? (https://direct.uber.com/)
Can you share screenshot?
Also, I recommend to use the custom oauth2 Bubble auth…
I can’t even get the token using production credentials. Could you please share a screenshot of how you set up Bubble’s API connector? I’m having difficulties knowing where to paste each value and each ID.
thank you
To get the token for production, you need to fill everything requested by uber direct first…
I already completed all the information requested by Uber Direct. Could you please explain how you successfully integrated Uber Direct API with Bubble’s API connector?
Thank you
First remove Authorization in shared header. Bubble will include it automatically with the authentication part.
But this is not the error you are seeing. And this belong to wrong settings in Uber Direct https://direct.uber.com/ and not in https://developer.uber.com/dashboard/ ?
Can you share screenshot of your direct account in dev tab?
Did you test with test keys?
Yes, I’m using Uber Direct Test Keys. I deleted the authorization in the shared header but still get the same error.
Like I said, the authorizaed in shared header is not the error for now.
Can you share a screenshot of your direct uber dev tab?
To give a little bit more details, when you go to the dev tab, you will need to click on (not sure how this is labeled in english) “Go to test” on the blue banner on top of dev informations. Once it’s done, you will get new keys (they are the test keys). This is what you need to use for testing. Not the first keys you see when you load the dev tab
Correct Jici
I’m using test keys and not production keys. I suspect that Uber direct may have a different scope for its sandbox environment.
No it’s not the case. I don’t have any issue. And tested with both keys too (just did it)
@Jici @alvarolo98 sorry im using NodeJS but here’s a screenshot. I use the production credentials and I get a perfect response but when I use the testing credentials I can “Invalid Scope Error”.
In your screenshot, the url you are using is v1 while you should use https://auth.uber.com/oauth/v2/token
You’re totally right, I took the wrong screenshot. I usually had it a v2 but I was trying anything and everything for like 6 hours straight yesterday.
FIXED FOR ME! I did find out the problem for the “Invalid Scopes” error. Now I can get tokens with my testing credentials. It was a problem with uber. Here’s is a screenshot with the email they sent me after I put in for a support ticket. Also to put in a support ticket go to developer.uber .com /docs/deliveries/support
