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
Response of the list shared link API for team folders
Hi, I observed a different response from list shared link API for those sub folders under a team folder.
There is a folder test0327 under a Team Folder, the path is /Team Folder For Integration...
mikechiu wrote:..., I got two different responses with/without Path-Root header.
...
Hi mikechiu,
It's normal, since by default (when nothing set) your Path-Root is your home folder. Let's recall your test folder is outside your home folder. So, without Path-Root set to your team space, the target folder is "invisible" and that's why "path/not_found". Opposite, when set, it's visible, but there is no any link set (make difference between shared folder and shared link) and that's why non erroneous empty result. 😉
Hope this clarifies the things to some extent.
Hi Здравко thanks for your reply for the Path-Root, makes sense to me.
But how can I understand the permission error when using id instead of shared folder id in both cases without Path-Root?
Cause for me these two are the same. And actually, there's a shared link existed if I use UserA as Select-User.
Thus for me, more reasonable result is not empty but permission denied since empty result will make false judgement.
mikechiu, I'm not some Dropbox system designer and that's why can only speculate on this. I agree that it's somehow confusing since not systematically documented (not yet at least). I just took a look on other posts from you and saw that you have created (or was trying to create) shared link on places where links are restricted. If the case here is something similar and I have to bet - you're trying to get link that's not supposed to be there at all and you get such error. In general using path, id, or namespace (wherever available, i.e. shared folder) should be the same. Probably some API imperfection. Let's hope will be fixed and/or documented properly.
Good luck.
Ops, just a moment: Do you mean that you have used a user that doesn't have access to there (doesn't matter it's admin - at that moment there is no admin, but just user)? If so, then the things are clear - just missing permission as stated by the error.
Hi Здравко , thanks for your quick reply!
Yes, the user that I used for Select-User is unable to access the target file/folder.
So that's why I am confused why not all upstream responses are the same.
And I totally agree with you regarding the imperfection of the API.
So here is what I am going to do, just use the response that I confirmed through the test and hopefully it won't change sometime.
Really appreciate your help. Thanks!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
