We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Dropbox APP Authorization Token Expires
Hello Forum Members, I have a project where I receive public URLs of files, and I save these files to a specific folder structure in Dropbox In my Dropbox account only. I'm using https://www.dropbox...
OAuth flow is a way to authenticate user (one or more) grant for particular application to access corresponding account(s). There is no any limitation in users count (if we ignore some possible provider specific limitations, but it's not protocol related). As I said for long term access, you need refresh token and the only way to get to such token is OAuth usage - Dropbox doesn't provide alternative by now - doesn't matter who is the user or how many are they.
When you will use only your own account, you don't need to implement the complete OAuth flow inside your application, but you need refresh part at least - it's mandatory. The actual authentication (the initial steps) can be performed once, by hands, outside the application and once you have the refresh token continue using it inside the application. For an example how you can perform the initial steps outside application and how you can perform refresh inside the application (you should implement the last step in PHP), take a look here.
Hope this sheds some more light.
Hi ABDUL Salam,
Long lived access token are deprecated long time ago already. Currently, generation of new such token is completely dropped - all new access token are short lived (If you have still some old you can kepp using it, not new).
For long term access and new token, you need refresh token received using OAuth flow with set offline access. May be you will want to implement refreshing in your PHP to use it continuously.
Hope this gives direction.
OAuth flow is a way to authenticate user (one or more) grant for particular application to access corresponding account(s). There is no any limitation in users count (if we ignore some possible provider specific limitations, but it's not protocol related). As I said for long term access, you need refresh token and the only way to get to such token is OAuth usage - Dropbox doesn't provide alternative by now - doesn't matter who is the user or how many are they.
When you will use only your own account, you don't need to implement the complete OAuth flow inside your application, but you need refresh part at least - it's mandatory. The actual authentication (the initial steps) can be performed once, by hands, outside the application and once you have the refresh token continue using it inside the application. For an example how you can perform the initial steps outside application and how you can perform refresh inside the application (you should implement the last step in PHP), take a look here.
Hope this sheds some more light.
Thanks Здравко That makes sense. Appreciate your detailed explaination.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
