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.
Greg-DB Thanks for the response!
We followed the guide you linked, and have some more information, but things do not work consistently still.
- Using the /files/list_folder API endpoint only returns 100 team folders. Our organization makes heavy use of team folders -- we have over 500 of them. Prior to the team spaces migration our team admin account had access to all 500+ of them. Is there a limit that got put in place for team spaces?
- Even for the team folders in which we have access (as per /files/list_folder), we cannot create new folders in them. Both /files/create_folder_v2 and /sharing/share_folder fail with a no permissions response.
- We did not used to have the Dropbox-API-Path-Root header in our requests. We added it in, but it does not seem to have any effect on the responses we receive. We set the header as {".tag": "root", "root": "<root_namespace_id>"}, with <root_namespace_id> coming from the /users/get_current_account API endpoint.
Does this provide some more info that could help narrow down the root cause? At the end of the day we're seeing significant errors in using Dropbox API in the way we were using it pre-team-space-configuration.
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.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
