The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can we bulk-invite users to a Bitbucket group after app-password retirement?

NVIDIA DLI
August 31, 2026

We manage private teaching-material repositories in the nvidia-dli Bitbucket Cloud workspace. The teachingkits group has read access to six private repositories, and our prior process was to add a list of users from a text file to that group via a script.

Our old script used this legacy endpoint with an app password:

PUT https://api.bitbucket.org/1.0/users/nvidia-dli/invitations

with:

{"email":"user@example.com","group_slug":"teachingkits"}

After moving to a scoped Bitbucket API token (admin:repository:bitbucket and admin:workspace:bitbucket), the endpoint returns HTTP 403. We also tested both Basic and Bearer authentication.

I found BCLOUD-24073, which states that the legacy /1.0/invitations endpoint does not support API-token authentication.

Is there a supported, scriptable replacement for bulk-inviting email addresses to a Bitbucket group or private repositories? If not, is there a migration path or workaround planned for Bitbucket Cloud Free workspaces?

We need to keep the repositories private; manually adding each user to the group is our current workaround.

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Mihai_LeanZero
Atlassian Partner
September 5, 2026

BCLOUD-24073 is Gathering Interest. One vote, no fix version. That v1 endpoint is not coming back, so I'd stop designing around it.

Go org-level, not Bitbucket-level:

POST https://api.atlassian.com/admin/v2/orgs/{orgId}/users/invite

Bearer auth, so a scoped token works. Body takes emails plus additionalGroups. That second field is the missing piece. v1 of that API could not add groups during an invite. v2 can. Needs a paid subscription on the org.

None of it applies unless the workspace is linked to an Atlassian organization. Linked, the org holds your groups and the invite API reaches them. Unlinked, they stay Bitbucket-native and it is the v1 endpoint again.

additionalGroups wants group IDs, not names. And v1 of the org API dies 30 June 2026.

0 votes
Arkadiusz Wroblewski
Community Champion
September 1, 2026

Hello @NVIDIA DLI 

Have you tried POST /v2/orgs/{orgId}/users/invite ?

Atlassian has moved user/group administration for newer Bitbucket workspaces toward Atlassian Administration.

Best,

Arek🤠

DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events