We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
API get_metadata returns 429 text/html
Recently we've been getting text/html 429 responses from the get_metadata endpoint, when we specify
Accept: application/json
header.
Response:
{:request=>{:url=>"https://api.dropboxapi.co...
To follow up here, the team confirmed that they found and resolved the issue with the excessive 429 responses with HTML bodies as of late Friday. Apologies for the inconvenience.
Greg-DB
Dropbox Staff
Dropbox StaffThanks for the report. It looks like we may be using a generic HTML error page in some rate limiting cases. We'll look into it.
Thanks, keep me posted please!
We're having the same issue. Suddenly some of our internal applications are crashing due to this. It disrupts our work very seriously. I dont feel me made any abusive calls.
Our apps are set in "development" status and used only by ourselves.
- Greg-DB
UlfFahlen Thanks for the additional report. We're looking into it. Note that the development/production status of your app wouldn't affect this.
The problems have arised when checking if a file exists on dropbox. In our SDK:
$dropbox->has($file)
This calls get_metadata on the API.
We used this to determine if a file existed before uploading or deleting it. We have removed it from our script now and instead added an exception to handle the errors when trying to delete a file already deleted. The script now works, but the rate limit set on this API call is very limiting (and new).
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
