We’re Still Here to Help (Even Over the Holidays!) - find out more here.
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, 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.
