According to the documentation (https://developer.atlassian.com/bitbucket/api/2/reference/resource/) there are no endpoints for listing or modifying groups, group members and group repository permissions.

      There was group support in v1 but this version is going to be deprecated soon
      (https://confluence.atlassian.com/bitbucket/groups-endpoint-296093143.html and
      https://confluence.atlassian.com/bitbucket/group-privileges-endpoint-296093137.html)

            [BCLOUD-16556] No API support for groups in v2

            Is there a way to change the Project property of a Repository with API?

            I've tried using the internal API as described above, but not working.

            Aaron Bauman added a comment - Is there a way to change the Project property of a Repository with API? I've tried using the internal API as described above, but not working.

            Issue BCLOUD-17103 was marked as a duplicate of this issue.

            Patrick Wolf - Atlassian (Inactive) added a comment - Issue BCLOUD-17103 was marked as a duplicate of this issue.

            The 1.0 /groups and /group-privileges APIs will remain available until a proper 2.0 replacement is created.

            Patrick Wolf - Atlassian (Inactive) added a comment - The 1.0 /groups and /group-privileges APIs will remain available until a proper 2.0 replacement is created.

            Create new OAuth Consumer solved the problem. Thanks Atlassian support.

            Tran Tien dung added a comment - Create new OAuth Consumer solved the problem. Thanks Atlassian support.

            Yes, I have exactly the same issue. I discussed with Bitbucket support about it. It seems it’s a bug and they are investigating.

            In the meantime, they gave me a workaround: the problem only concerns authentication with OAuth consumers associated with teams. OAuth consumers associated to personnal accounts are working.

            Aurélie VALERY added a comment - Yes, I have exactly the same issue. I discussed with Bitbucket support about it. It seems it’s a bug and they are investigating. In the meantime, they gave me a workaround: the problem only concerns authentication with OAuth consumers associated with teams. OAuth consumers associated to personnal accounts are working.

            Seen like group endpoint api not even work in v1 as well. Do anyone got a same issue?

            Tran Tien dung added a comment - Seen like group endpoint api not even work in v1 as well. Do anyone got a same issue?

            Thank you Patrick Wolf for your feedback. In addition, I created a ticket on the help center and someone helped me find answers to my problems.

            In case someone else is interested: once the user has joined at least one group, we can still invite him to other groups without any other invitation, by using the following endpoint:

            PUT /1.0/groups/{team}/{group}/members/{user UUID}
            

            But still, we had to work a lot on our automation and in urgence to make this work again, I was expecting some communication before the change occured.

            Aurélie VALERY added a comment - Thank you Patrick Wolf for your feedback. In addition, I created a ticket on the help center and someone helped me find answers to my problems. In case someone else is interested: once the user has joined at least one group, we can still invite him to other groups without any other invitation, by using the following endpoint: PUT /1.0/groups/{team}/{group}/members/{user UUID} But still, we had to work a lot on our automation and in urgence to make this work again, I was expecting some communication before the change occured.

            If you use these APIs, please refer to BCLOUD-18913

            Michael Nascimento Santos added a comment - If you use these APIs, please refer to BCLOUD-18913

            Hi, avalery

            To prevent users from farming usernames via the API by programmatically adding users to a group and recording which users are automatically added all users must be invited to join the account using their email address. Users must then explicitly accept the invitation before they are added to a group. Once they accept invitation the user will be added to group.

            PUT /1.0/users/{uuid}/invitations
            
            body params: email and group_slug
            

            Note: this is a 1.0 endpoint that will continue to be available.

            Regards,

            Patrick

            Patrick Wolf - Atlassian (Inactive) added a comment - Hi, avalery To prevent users from farming usernames via the API by programmatically adding users to a group and recording which users are automatically added all users must be invited to join the account using their email address. Users must then explicitly accept the invitation before they are added to a group. Once they accept invitation the user will be added to group. PUT /1.0/users/{uuid}/invitations body params: email and group_slug Note: this is a 1.0 endpoint that will continue to be available. Regards, Patrick

            I have no news from my message, but still have the problem and it’s really blocking us. Does anyone has the same problem?

            Aurélie VALERY added a comment - I have no news from my message, but still have the problem and it’s really blocking us. Does anyone has the same problem?

              Unassigned Unassigned
              327db0747024 Bart Haalstra
              Affected customers:
              60 This affects my team
              Watchers:
              68 Start watching this issue

                Created:
                Updated:
                Resolved: