We have a big problem on our hands when it comes to obtaining all of the collaborations a user created inviting others to their content. There simply is no quick way of doing this, especially on users having massive folders. We discovered that the GET action on the /Folders endpoint has an available request field called “hascollaborations” which indicates whether the folder has any collaborations. I really hoped we could leverage this to cut down on the unnecessary calls to the /Folders/{folderId}/collaborations endpoint if the folder being iterated over had no collaborations, but unfortunately it returns “true” even if the only collaborations present were inherited from a parent folder. Unfortunately, because the way our enterprise is structured with all user content nested under root folders, and root-folder-level collaborations issued to our DLP scanners, this has the unwanted consequence of every single subfolder returning a “hascollaborations” value of “true”, triggering us to make unnecessary calls to get the collaborations collection, only to find that none of them are on the specific folderId being processed.

Please introduce a new fields collection value for the /Folders endpoint that indicates whether that specific folder has any collaborations of its own, i.e. not inherited from a parent? The existing “has_collaborations” field does us no good in its current form, and we really need to figure out a way to gather those collaborations more efficiently.