We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Large number of new errors when making write actions via Dropbox API
Hi folks, We’re having some trouble with our Dropbox API integration and getting new errors from the Dropbox API. Some backstory: we’ve been using the Dropbox API to manage shared folders acr...
Followup here as we've now resolved this issue and want to share our findings if anyone else runs into the same problems:
The issue ultimately turned out to be the lack of the Dropbox-API-Path-Root header. However, even after including it still failed the same way because we didn't JSON encode the contents of the header prior to handing things off to our HTTP library. We also never were able to (intentionally or accidentally) generate the errors documented in https://www.dropbox.com/developers/reference/path-root-header-modes so it was difficult to diagnose we were not using the header properly.
Hi lfranchi_pilot,
Your error doesn't come from missing scopes. 😉 There is another error that comes in place for missing scopes - "missing_scope". Currently, this is not the case.
Your error denotes that you don't have permission to create regular folder on the place where you try, not something else! There may be different reasons, but typical are a try to create subfolder in a folder where user doesn't have write permission or try create regular folder on place where, according user' account, it's impossible (in team root scope for some accounts). Check the permissions that user (likely your account) has and if they changed recently (including related to possible account type change).
Hope this gives direction.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
