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

Ashley B.15's avatar
Ashley B.15
Helpful | Level 7
9 years ago

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) Request-URI Too Large. the cursor returned from the end point is 31279 characters in length the entries count: 2000 I've tried to reproduce this but can't Do you know why this might be occuring ?

 

Thanks

  • 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.)

     

     

  • Greg-DB's avatar
    Greg-DB
    Icon for Dropbox Staff rankDropbox Staff

    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.)

     

     

About Dropbox API Support & Feedback

Node avatar for Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

5,882 PostsLatest Activity: 3 years ago
325 Following

If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.

For more info on available support options for your Dropbox plan, see this article.

If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!