You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
help: long-live tokens for dropbox app
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 t...
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
Dropbox Staff
Dropbox StaffThe 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.
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
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.
dpellic996 wrote:...
sorry for the confusion, i'm not very into these things and I find this very complicated!
...Hi dpellic996,
As Greg already noted, you can initiate and perform authorization (granting access to particular account data) either by hand (without redirect URI; copy-past access code by hand) or automated (automatic redirect from Dropbox site back to your application). An example, that uses redirect URL and that you can take a look on, can be seen here. 😉 I believe this will give you idea how the things could go.
Hope this helps.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
