cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Share your feedback on the Document Scanning Experience in the Dropbox App right here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: Adding group to the Team Folder using API not working

Adding group to the Team Folder using API not working

petrovski
Explorer | Level 3
Go to solution

Hello,

I am having issues with the dropbox api v2

I am trying to add group to team folder using the 2/sharing/add_folder_member

I am sending the request with this body:

{
  "shared_folder_id": :team_folder_id,
  "members": [
    {
      "member": {
        ".tag": "dropbox_id",
        "dropbox_id": :group_id
      },
      "access_level": {
        ".tag": "editor"
      }
    }
  ]
}

, and headers:

Authorization [Bearer :team_member_file_access_token],
Dropbox-API-Select-User [:business_account_owner_team_member_id]

The provided user in the headers is member of the group

This api call was working fine before, but since the last week always gives access_error - not_a_member error.

Can you please tell me how to fix this or if there is another way to add group to team folder?

Thanks,

Borche

 

1 Accepted Solution

Accepted Solutions

Greg-DB
Dropbox Staff
Go to solution

[Cross-linking for reference: https://stackoverflow.com/questions/51929171/adding-group-to-the-team-folder-using-api-not-working ]

 

I believe this is due to a change in how our membership model works for operations in team folders like this. 

We're looking into that change, but to make this work, please use the "Member file access" feature with an app with the "team member file access" permission, and use ....

View solution in original post

1 Reply 1

Greg-DB
Dropbox Staff
Go to solution

[Cross-linking for reference: https://stackoverflow.com/questions/51929171/adding-group-to-the-team-folder-using-api-not-working ]

 

I believe this is due to a change in how our membership model works for operations in team folders like this. 

We're looking into that change, but to make this work, please use the "Member file access" feature with an app with the "team member file access" permission, and use ....

Need more support?