Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Cynthia B.2
10 years agoNew member | Level 1
500 internal Server Error https://api.dropboxapi.com/2/files/list_folder/continue
I've using the following endpoint to retrieve files and folders:
https://api.dropboxapi.com/2/files/list_folder this returns 2000 entries and then get hasmore = true and the cursor. I then user this for the following endpoint :
https://api.dropboxapi.com/2/files/list_folder/continue
Everytime it returns internal server errror with no error detail. Can you help?
Thanks
37 Replies
Replies have been turned off for this discussion
- sfbrad9 years agoExplorer | Level 4Thanks for the reply.
X-Dropbox-Request-Id: 7c19057695051c5944f59c0644e3ae1a - Greg-DB9 years ago
Dropbox Community Moderator
Thanks! That's helpful. That's the same issue as reported by thedeck earlier in this thread. I'll follow up here once I have an update. - Ashley B.159 years agoHelpful | Level 7
Hi,
Is there any update to the orginal post made by Cynthia back in August last year? I have been asked to follow up on this?
Thanks
- Greg-DB9 years ago
Dropbox Community Moderator
The team has been working to resolve these issues, but the error rate is still non-zero.
These multiple issues appear identically to the API client though, so if you need us to check on a specific issue, please open a ticket with a new X-Dropbox-Request-Id value:
https://www.dropbox.com/developers/contact - chuffy9 years agoNew member | Level 2
Hi, Any update on this? It seems I have the same problem. Two request ids
d518feba1197fddb0ddfac99075a8404
12f63fb940bdaa85831b40757575506a
Are these the same issue, or should I open a new ticket?
- Greg-DB9 years ago
Dropbox Community Moderator
chuffy It doesn't look like that's quite the same issue, so please do open a ticket:
https://www.dropbox.com/developers/contact
Thanks in advance!
- Greg-DB9 years ago
Dropbox Community Moderator
Regarding the errors reporting by thedeck and sfbrad, these 500s can be caused by certain file metadata not being available yet, at the time of the API call. The team has been working on improvements around this. When this information is still not available, Dropbox will now be returning 429s, to instruct the app to call back later, when the metadata will be available.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
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, Facebook or Instagram.
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!