Oauth This app is not valid

falitjain

Description of Issue:
I’ve created a new Dropbox Scoped App (Team API) with the following details:
App key: z5m1afbrxsdbzf8
Redirect URI (registered in App Console):
https://357b68995e62.ngrok-free.app/syncorg/dropbox/oauth
Permissions selected: team_info.read, members.read, members.write, groups.read, groups.write
When I try to authenticate using this OAuth2 URL:
https://www.dropbox.com/oauth2/authorize?client_id=z5m1afbrxsdbzf8&response_type=code&redirect_uri=https://357b68995e62.ngrok-free.app/syncorg/dropbox/oauth&state=8eff1547-cbde-439c-9f8b-feba6d7fcb51&token_access_type=offline&token_access_type=team&scope=team_info.read members.read members.write groups.read groups.write&include_granted_scopes=team
I have tried with simpler urls ie. without scopes , state etc

I consistently get: This app is not valid 
What I’ve Tried:
Verified that the redirect_uri matches exactly what’s in the console.
Added the correct scopes in the Permissions tab.
Tried without adding the scopes in oauth url
Tried with and without include_granted_scopes=team.
Confirmed I’m using the App Key (not the secret).
Question:
Why is this happening?

Is the error due to not having a Development Team linked (0/1)?Do I need a Dropbox Business Sandbox team before I can use token_access_type=team?

DB-Des

Hi @falitjain 

The “This app is not valid” error is occurring because your request includes parameters that aren’t valid for your app’s current configuration.

In particular, the value token_access_type=team isn’t supported — this isn’t a valid parameter for the Dropbox OAuth flow. Additionally, it looks like you’re including scopes in your scope parameter that haven’t yet been enabled for your app.

As noted in the documentation for /oauth2/authorize, the scope parameter can only include a subset of the scopes already selected in your App Console. If you’d like to use additional scopes, you’ll need to first enable them in your app’s settings before including them in your authorization request.

Once those adjustments are made, your authorization flow should work as expected.