replacements for deprecated user-scoped permission endpoints being removed in CHANGE-2770

[Roman Chametka]

Hello,

I'm working on a Bitbucket Cloud integration and need clarification on several critical API endpoints that are being deprecated as part of CHANGE-2770.

Deprecated Endpoints in Question:

1. GET /user/permissions/workspaces - Documentation
2. GET /user/permissions/repositories - Documentation
3. GET /repositories - Documentation

The suggested workspace-scoped alternatives appear to be:

• /workspaces/{workspace}/permissions/repositories
• /workspaces/{workspace}/permissions/repositories/{repo_slug}

However, these alternatives have a critical limitation: they require the authenticated user to have admin permissions on the repository (as stated in the documentation: "Only users with admin permission for the repository may access this resource").

Our integration needs to allow non-admin users to:

• List all repositories the authenticated user has access to (across all workspaces)
• Discover which workspaces they have access to and their permission level in each workspace
• Check their own permission level (read/write/admin) on specific repositories

The deprecated endpoints were perfect for this because they:

• Returned data scoped to the authenticated user's access
• Didn't require admin permissions
• Allowed filtering (e.g., GET /repositories?role=member)

Questions:

1. What are the planned replacement endpoints that will allow non-admin users to:
   • List all repositories they have access to?
   • Check their own permission level on repositories?
   • List workspaces they're members of with their permission levels?
2. Will there be user-scoped endpoints (similar to the deprecated ones) that return data based on the authenticated user's access without requiring admin permissions?
3. What is the timeline for announcing/releasing these replacement endpoints?
4. Is there a recommended workaround that doesn't require admin access for users to check their own permissions?

Thank you