Retrieving branch restriction rules , including the required approval count , via the Bitbucket Cloud REST API currently requires admin:repository:bitbucket. This is excessive for a read-only operation that is:

•  Visible to any user in the Bitbucket UI;
•  Accessible on Bitbucket DC with only repo:read
The internal endpoint previously used as a workaround (/api/internal/repositories/.../merge-restrictions) was recently blocked for bearer token authentication.
Ask: Either:

 1.  Expose the required approval count in the standard PR API response (GET /2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pr_id} }}) without {{admin:repository:bitbucket; or
 2.  Reduce the branch restriction read endpoint scope to read:pullrequest:bitbucket or repository:read, consistent with Bitbucket DC.

Use case: Marketplace apps displaying PR merge readiness require admin-level access for a purely informational read — creating an unnecessary security barrier for users.