Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
This same API has been working solidly for years, but now in the past 2-ish days it has been returning more and more errors.
Sometimes it works for quite a while, but sometimes it keeps erroring for every single request.
This is happening to several dozen people at the moment, although all using the same app.
SDK doesn't seem to matter, as I'm seeing it on very old as well as the very latest versions (Objective-C/iOS).
Couldn't find anyone else reporting this and all the status pages and blogs aren't mentioning this either, so I'm assuming it's a new bug/issue.
More error context:
DropboxInternalServerError[{ ErrorContent = nil; RequestId = 69738b83eefc634b2c5058b038aa0dd0; StatusCode = 500; UserMessage = nil; }];
This should be resolved now. Please let us know if you're still seeing any issues. Thanks!
Thanks for the report! We're looking into it. I'll follow up here once I have an update on this.
Just in case this information is useful, there are about 50 users every day, using about 10-20k API calls total.
The issue might be worse the more API calls there are, but this is purely a guess and nothing more.
Thanks for the information!
This should be resolved now. Please let us know if you're still seeing any issues. Thanks!
The errors actually "magically" went away about 24+ hours after reporting it.
Can you give any details as to what was wrong and if anything was actually fixed?
I'm also wondering if it was caused by the legacy permissions/scopes, which I migrated to the new system, so if this was actually what fixed it, but just rolled out slowly/took a day to apply?
Thanks for confirming! This was an issue with the search backend that the engineering team worked to resolve. This wasn't related to the scopes migration.
Is it possible that this issue has happened again?
My nightly script began failing on the 8th of December with error 500 Internal Server Error when accessing https://api.dropboxapi.com/2/files/search.
The same script has been running successfully for months.
Thanks in advance for any information or advice.
@jenkinspps Can you share a few sample X-Dropbox-Request-Id response header values for the issue you're currently seeing? Thanks in advance!
Thanks @Greg-DB.
My script did not log the response headers but I've made it do so now.
I re-ran it a few minutes ago and the Request-Id was 7ea42fec60c3447e9939ec1565fda7dc.
The error was still 500.
Hi there!
If you need more help you can view your support options (expected response time for a 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!