Bitbucket
Connect Bitbucket Cloud with a scoped Atlassian API token or an access token and read repositories, commits, pull requests, tags, branches and Pipelines runs.
A Bitbucket connection reads Bitbucket Cloud repositories with a read-only
token. It calls only api.bitbucket.org. Bitbucket Data Center is not
supported. For the tables, columns and limits that every forge shares, see the
Git overview.
Preview
Git connections are in Preview and are enabled on request: contact
support@xentropy.ai. Until Bitbucket is enabled for your account it is not
offered in the forge selector, and its reads fail with PROVIDER_DISABLED.
Create a read-only token
App passwords no longer work
Bitbucket stopped accepting app passwords in 2026. Use an Atlassian API token with scopes, or an access token.
You can use either kind of token:
- Atlassian API token with scopes (recommended). It reads every workspace your Atlassian account can read. Xentropy signs in with your Atlassian account e-mail and the token.
- Workspace, project or repository access token. It is bound to that workspace, project or repository, not to a person. Workspace access tokens need a Bitbucket Premium plan.
To create an API token:
To create an access token instead, open the repository's, project's or workspace's settings in Bitbucket, then Access tokens, choose Create access token, and select Read permissions for repositories, pull requests and pipelines only.
Token permissions
The form lists these scopes with a copy button. An API token's scopes do not include each other, so select every one.
| Scope | Unlocks |
|---|---|
read:user:bitbucket | Who the token belongs to, for the connection test |
read:workspace:bitbucket | The workspaces the token can read |
read:repository:bitbucket | Repositories, commits, tags, branches and contributors |
read:pullrequest:bitbucket | Pull requests |
read:pipeline:bitbucket | Pipelines runs |
Set up the connection
bitbucket.org/<workspace>. Left empty, the connection lists every workspace the token can read.Repository full names are workspace/repository.
Connect with Bitbucket (sign-in with your Atlassian account) appears only when Bitbucket sign-in is available for your account. Until then, connect with a token as above.
Resources
| Resource | Available | Notes |
|---|---|---|
repositories | Yes | Repositories you are a member of, in the workspace or in every workspace |
commits | Yes | Commits of every branch, or of the branch you choose, in the date range |
pull_requests | Yes | Open, merged, declined and superseded; declined and superseded read as closed |
issues | No | Bitbucket Cloud removed its issue tracker API |
releases | No | Bitbucket has no release objects: read tags instead |
tags | Yes | |
branches | Yes | |
contributors | From commits | Bitbucket has no contributors list: commits in the date range, counted per author |
pipeline_runs | Yes | Bitbucket Pipelines runs |
Choosing issues or releases fails with VALIDATION_FAILED before any
request is sent.
Columns left empty
| Resource | Empty columns |
|---|---|
repositories | archived, stars, forks, open_issues, pushed_at |
commits | committer_name, committer_email, additions, deletions |
pull_requests | closed_at, merged_at, additions, deletions, changed_files |
branches | protected |
pipeline_runs | name, started_at |
Bitbucket's pull request list has no close or merge time: chart merged pull
requests by updated_at.
Limits
An Atlassian API token can make 1,000 requests per hour to repository endpoints, counted per user. Access tokens of larger paid workspaces get a higher limit. Bitbucket answers 429 when the limit is reached and does not say how long to wait, so Xentropy waits 60 seconds before it tries again. Pages hold at most 50 rows. See Limits and refresh for pages, rows and deadlines.
Errors
| Response | Code | Cause | What to do |
|---|---|---|---|
| 401 | PROVIDER_ACCESS_DENIED, stage auth | The token expired, was revoked or mistyped, the e-mail does not match an API token, or an app password was used | Create an API token (with your account e-mail) or an access token, and choose Replace configuration |
| 403 | PROVIDER_ACCESS_DENIED, stage permissions | A scope is missing. details.missingScopes names it, for example read:pullrequest:bitbucket | Create a new token with every scope above; scopes cannot be added later |
| 404 | NOT_FOUND | The repository or workspace does not exist, or the token cannot see it | Check the workspace ID and the repository name, and the token's workspace, project or repository |
| Redirect | NOT_FOUND | The repository moved or was renamed | Select the repository under its new name |
| 429 | RATE_LIMITED | The hourly limit is used up | Retry after details.retryAt; scheduled refreshes wait by themselves |
| — | VALIDATION_FAILED | issues or releases was chosen | Choose another resource; use tags for releases |
Gitea
Connect gitea.com with a read-only access token and read repositories, commits, pull requests, issues, releases and Actions runs.
Azure DevOps
Connect Azure DevOps Services with an organization-scoped read-only personal access token and read Azure Repos, pull requests, work items and Azure Pipelines builds.