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
Fail updating folder member
Hi, I am running into a problem when calling sharing/update_folder_member . The error is {"error_summary": "access_error/not_a_member/.", "error": {".tag": "access_error", "access_error": {".ta...
The /2/sharing/update_folder_member endpoint does support the Dropbox-API-Select-Admin header, but only in the "Team Admin" mode, meaning it can "access content of team folders and team spaces but not the team members' home namespaces". So, for example, if that namespace is for a shared folder in the account's home namespace, you can't use the Dropbox-API-Select-Admin header and would need to instead use the Dropbox-API-Select-User header.
As for the version of the call where you do use the Dropbox-API-Select-User header, as Здравко noted, it looks like that did succeed, but returned a confusing warning message. For reference, if you print out the status code, I expect it is a 200, indicating success. I'll ask the team to look into this to correct that confusing warning message though.
Здравко oh, yes, I think you're right, the response of the list folder members showing that the access type is viewer now. And yes the message is pretty confusing tho. 😂
And I was wondering why the previous 3 requests failed ? As the document mentioned this API accepts Dropbox-API-Select-Admin header and actually I'd prefer to using this header.
Still need more information on it.
Greg-DB
Dropbox Staff
Dropbox StaffThe /2/sharing/update_folder_member endpoint does support the Dropbox-API-Select-Admin header, but only in the "Team Admin" mode, meaning it can "access content of team folders and team spaces but not the team members' home namespaces". So, for example, if that namespace is for a shared folder in the account's home namespace, you can't use the Dropbox-API-Select-Admin header and would need to instead use the Dropbox-API-Select-User header.
As for the version of the call where you do use the Dropbox-API-Select-User header, as Здравко noted, it looks like that did succeed, but returned a confusing warning message. For reference, if you print out the status code, I expect it is a 200, indicating success. I'll ask the team to look into this to correct that confusing warning message though.
About Discuss Dropbox Developer & API
Make connections with other developers
