sharing/list_file_members/batch won't return cursor

Hi noacaspi,

Take in mind that inherited users and groups are not included in the result, and permissions are not returned while using batch! On using non batch variant inherited users are included by default. 🤔 Can this be the reason for different results, you are getting? Check to be sure. 😉

Hope this helps.

noacaspi That's correct, the /2/sharing/list_file_members/batch and /2/sharing/list_file_members[/continue] endpoints operate differently. The /2/sharing/list_file_members/batch endpoint does not return a cursor, for instance. Refer to the descriptions for those routes and the documented fields for more information on that. There aren't any other options beyond what is documented there.

---

Greg-DB wrote:

... The /2/sharing/list_file_members/batch endpoint does not return a cursor, for instance. ...

---

Greg-DB, Here can be seen:

Does this mean that the documentation is "broken"? 🙂

Здравко Apologies, I was referring to the lack of a top-level cursor from /2/sharing/list_file_members/batch, as compared to the SharedFileMembers.cursor returned by /2/sharing/list_file_members. As you pointed out though, there is the nested ListFileMembersIndividualResult.ListFileMembersCountResult.cursor though, for use with /2/sharing/list_file_members/continue for the corresponding file.