help: long-live tokens for dropbox app

Question

Hello everyone,I know that there are other issues related to this but I did not find anything that really helped me.I'm trying to upload images (.png) from my PC to dropbox via an application that I already created.I'm doing this using a python script I wrote. The part that concerns the dropbox upload is the following:
def upload_to_dropbox(file_path, dropbox_token, dropbox_folder):
&nbsp; &nbsp; dbx = dropbox.Dropbox(dropbox_token)
&nbsp; &nbsp; with open(file_path, 'rb') as f:&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; filename = os.path.basename(file_path)&nbsp; &nbsp; &nbsp; &nbsp; dropbox_path = dropbox_folder+filename&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; dbx.files_upload(f.read(), dropbox_path)
&nbsp;
&nbsp; &nbsp; shared_link_metadata = dbx.sharing_create_shared_link(dropbox_path)&nbsp; &nbsp; return shared_link_metadata.urlIn doing this I'm using an access token that I generate in the Console App. This token begins with "sl" and I know that expires in few hours.&nbsp;Could you please provide me support on how to get a long-live token, or how to refresh automatically the token I'm using?Thank you in advance 🙂D.

Greg-DB · Answer

Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information on this migration here.

Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access tokens as needed, without further manual user intervention. You can find more information in the OAuth Guide and authorization documentation. There's a basic outline of processing this flow in this blog post which may serve as a useful example.

The official Dropbox SDKs can handle this automatically for you. For the official Dropbox Python SDK, you can find examples of this flow at the following links:

https://github.com/dropbox/dropbox-sdk-python/blob/main/example/oauth/commandline-oauth-scopes.py
https://github.com/dropbox/dropbox-sdk-python/blob/main/example/oauth/commandline-oauth-pkce.py

dpellic996 · Answer

Thank you but I have still a doubt on this..I don't know any REDIRECT URI.. how can I get one? What's the criterion I could use to choose one? Actually is the only thing I still don't have.

Greg-DB · Answer

The redirect URI is the location where the user should be sent after they authorize the app to access their account. It should be a URI controlled by your app and defined by you as the developer of the app. That being the case, I can't tell you exactly what yours should be, but for example, if you're building a web app and your redirect URI for your development environment looks like http://localhost/auth, then it would typically look like https://example.com/auth in the deployed environment. For reference, it is optional; you can opt to not use a redirect URI, in which case you would omit that parameter and the user would need to manually copy/paste the authorization code. For instance, the Python SDK samples I linked to don't use a redirect URI.

dpellic996 · Answer

So, if I got it right, using a redirect URI is the only way for generating a refresh token automatically (i.e. not manually by authorizing by myself)?sorry for the confusion, i'm not very into these things and I find this very complicated!D.

Greg-DB · Answer

No, a redirect URI is not required to get a refresh token. Whether or not a redirect URI is used though, the manual authorization step does need to be handled by the user manually in order to authorize the app to access their account and receive a refresh token. This only needs to be done once per account though; the refresh token can then be stored and re-used programmatically without the user present.

Forum Discussion

help: long-live tokens for dropbox app

About Dropbox API Support & Feedback

Related Content

Tokens sin vencimiento

Dropbox Paper

como crear un token

ACCESS TOKEN CADUCA

Cambiar Token

Recent Discussions

Using the Javascript Chooser API in a Web Extension

How to add the entire team to team folder by api

API Upload .HEIC and convert to JPG

Invalid Folder Name with Team API

Zapier - 409 error path/not found