API to enable the Bitbucket "repository overview widget" (properties/sonarcloud/disabled) at scale

Hi Sonar team,

We manage ~500 repositories in a single Bitbucket Cloud workspace, all analyzed on SonarQube Cloud. We can already fully automate everything via API except turning on the repository overview widget, and we’d like to request an API for it.

What we automated successfully (works great):

  • Project creation: POST sonarcloud.io/api/projects/create
  • Project ↔ Bitbucket repo binding: POST api.sonarcloud.io/dop-translation/project-bindings with {projectId, repositoryId} → 201. This enables PR decoration.

What has no API — the widget toggle:
The “Show repository overview widget” checkbox (Repository settings → SonarQube Cloud → Settings) is the only step left that we cannot do server-to-server. After investigating, we found it is not stored in SonarQube Cloud at all — it is a Bitbucket application property under the Connect app key sonarcloud:

PUT api.bitbucket.org/2.0/repositories/{workspace}/{repoUuid}/properties/sonarcloud/disabledfalse

That property is writable only by the SonarQube Cloud Connect app’s signed JWT (from the settings iframe). No Bitbucket user/admin token can write it (403 “does not support authentication using the provided token”), and there is no SonarQube Cloud API endpoint for it (api/alm_settings/* → 404; not present in api/webservices/list; dop-translation only covers the binding).

The ask:
Please expose an API to set this widget flag per project/repository — ideally alongside the existing dop-translation/project-bindings endpoint (e.g. a showRepositoryOverviewWidget field on the binding, or a dedicated endpoint). For teams onboarding hundreds of repos, clicking a checkbox per repo in the browser is the only remaining manual step, and browser automation is not a viable long-term path given the Atlassian Connect → Forge transition (Connect end-of-support Dec 2026).

Happy to share the full technical breakdown if useful. Thanks!

Hi @Gelver_Castro,

You’re right, there’s currently no API for this. The “Show repository overview widget” flag lives on Bitbucket’s side as an Application property, and toggling it requires interactive OAuth consent from the user, not just an admin token, that’s also why your admin token got a 403, rather than it being a permissions gap. Current (manual) process is documented here.

No workaround to offer at the moment.

Since you’re already had some interaction with our team on the Forge migration thread, with greater context on this request, I’ll flag this specific use case (bulk onboarding across 500 repos) to the developers working on the Bitbucket integration.

Cheers,

Stevan