Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Endpoint /workspaces/<workspace>/permissions/repositories returning HTTP 500


I am a Bitbucket administrator and related to an audit we are asked to provide a list of users and which repositories each has write access to. Since there is no support for this in the UI I am forced to use the API to accomplish this task.

The documentation seems to indicate that the endpoint I am looking for is at:<slug>/permissions/repositories

However all calls to this endpoint return an HTTP 500 with a message like the following:

{"type": "error", "error": {"message": "Something went wrong", "id": "6f4a90adf86646fb8ed17c9df9ca2825"}}

Calls to<slug>/permissions work fine but don't include the information I need. 

Since this is in the cloud I have no visibility into what is happening on the server so I am pretty stuck at the moment.


I can also view the permissions at<slug>/permissions/<slug>

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 24, 2021

Unfortunately this is a known issue in that this page times out for large teams.

I suggest watching/voting for this public bug:

As a work-around you can check the permissions for each repository individually with this API (basically append the repo slug to the path you're using).

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events