You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Api now returning path not found
I am using the API: https://api.dropboxapi.com/2/files/get_metadata With a body of {"path":"FILENAME","include_media_info":false,"include_deleted":false,"include_has_explicit_shared_members":fa...
Hi there,
I am having the exact same issue. I have raised a ticket with Dropbox for this. I think the responses already received here are not fully taking into consideration your comment that nothing has changed, code or directory paths. For me, nothing has changed and I am receiving the same errors. I suspect this may have something to do with the introduction of the new 'personal' and 'team' paths, where the folder root has been essentially split in two (a rough description I know). Earlier in the week I had to fix a number of Zapier integrations with DropBox that started to error at the same time as my HTTP API integrations. In Zapier I had to redefine the 'from path' for each with a definition of the root being 'personal' or 'team'. This was new as of last week.
Furthermore, I have done some testing with the DROPBOX API Explorer and I have noticed that a lot of my team directories are no longer visible when using it to hit the 'list folder' API. For the folders that are visible, my HTTP API calls work, for those that are not I receive an error similar to yours.
I will let you know if I receive anything useful back from Dropbox support.
Greg-DB
Dropbox Staff
Dropbox Staffcoadyg From your description, it sounds like you're referring to your team using the "team space". You'd need to set the "Dropbox-API-Path-Root" header to your 'root_namespace_id' as described in the Team Files Guide to be able to access the contents of the team space.
Hello Greg,
Thank you for the document. Educating myself on the topic of root namespace, their ids and the related HTTP headers did the trick. We use the Team Space configuration so adding the header worked for my API calls.
One comment that I'd like to add is that before October this wasn't a requirement, i.e. The same calls were working before adding these headers. So something in the mix has changed (moved from optional to mandatory, or some default behaviour has changed).
Thanks again
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
