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
The remote server returned an error: (414) Request-URI Too Large.
I'm using the current end point to retrieve a users folders and files: https://www.dropbox.com/developers-v1/core/docs#delta I get the following error The remote server returned an error: (414) ...
Hi Ashley, the cursor can get very large like this when the account has many shared folders. The 414 error indicates that the URI (including the parameters, in this case, the long cursor) is too long to be processed.
Instead, you can include the parameters in the body of the API call, not on the URI itelf. For example, in curl, that would mean instead of doing something like this:
curl -X "POST" "https://api.dropboxapi.com/1/delta?cursor=CURSOR_HERE" \ -H "Authorization: Bearer ACCESS_TOKEN_HERE"you would do something like this:
curl -X "POST" "https://api.dropboxapi.com/1/delta" \ -H "Authorization: Bearer ACCESS_TOKEN_HERE" \ --data "cursor=CURSOR_HERE"(Also, I should note that API v1 is deprecated, so we recommend migrating to API v2 as soon as possible.)
Thanks. One other quick question. What is the best/prefered way for a desktop application to retrieve all users folders and files? Is it the deleta or metadata endpoint in v1 api?
I did move to v2 api but still waiting on feedback for this post :
Thanks again
Greg-DB
Dropbox Staff
Dropbox StaffIn API v1, /delta is preferred for listing all files and folders.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
