cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Want to learn some quick and useful tips to make your day easier? Check out how Calvin uses Replay to get feedback from other teams at Dropbox here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: How to customize API Request Authorization Webpage

How to customize API Request Authorization Webpage

trendmacdev
Explorer | Level 3
Go to solution

Hi:

    Our team uses Objective-C SDK to help users upload & download files from Dropbox.

    Here is the webpage when we request API authorization :

trendmacdev_0-1618214945505.png

    But we found some other app's webpage is different, for instance:

trendmacdev_1-1618215140482.png

    The content is much more concise than ours. How can we customize our webpage like this? Is the way we use the SDK incorrect?Please help us solve this problem.

 

Best regards

Cotin Yang

 

1 Accepted Solution

Accepted Solutions

Greg-DB
Dropbox Staff
Go to solution

The second screenshot shows an app using a legacy non-scoped permission, which is being phased out. The first screenshot shows a scoped app, which offers more granular information and control over the permission being requested. It is not possible to revert a scoped app to a non-scoped app. The best practice is to request the minimum scopes needed. What you have looks correct if you only need access to basic account information and the ability to read and write file data.

 

You can find more information on scopes in the OAuth Guide and authorization documentation.

View solution in original post

1 Reply 1

Greg-DB
Dropbox Staff
Go to solution

The second screenshot shows an app using a legacy non-scoped permission, which is being phased out. The first screenshot shows a scoped app, which offers more granular information and control over the permission being requested. It is not possible to revert a scoped app to a non-scoped app. The best practice is to request the minimum scopes needed. What you have looks correct if you only need access to basic account information and the ability to read and write file data.

 

You can find more information on scopes in the OAuth Guide and authorization documentation.

Need more support?