Docs
Connections

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:

  1. 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.
  2. 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:

Open your Atlassian account settings, then Security → API tokens, and choose Create API token with scopes.
Name the token and set an expiry date (at most one year).
Choose Bitbucket as the app, then select the read scopes in the table below. Scopes cannot be changed later, so select them all now.
Create the token and copy it.

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.

ScopeUnlocks
read:user:bitbucketWho the token belongs to, for the connection test
read:workspace:bitbucketThe workspaces the token can read
read:repository:bitbucketRepositories, commits, tags, branches and contributors
read:pullrequest:bitbucketPull requests
read:pipeline:bitbucketPipelines runs

Set up the connection

Open Connections, choose New connection, then Git, and choose Bitbucket.
Name the connection. Optionally enter the Workspace: the ID from bitbucket.org/<workspace>. Left empty, the connection lists every workspace the token can read.
For an API token, enter the Atlassian account e-mail. For an access token, leave the e-mail empty.
Paste the token and choose Test connection. The stages are Authentication (the token) and Repository access. The test lists the repositories the token can read.
Choose the repositories to allow, or none to allow every repository the token can read. Choose Save connection.
Open the connection, choose a resource, repositories and a date range, pick fields, preview 100 rows and save a dataset.

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

ResourceAvailableNotes
repositoriesYesRepositories you are a member of, in the workspace or in every workspace
commitsYesCommits of every branch, or of the branch you choose, in the date range
pull_requestsYesOpen, merged, declined and superseded; declined and superseded read as closed
issuesNoBitbucket Cloud removed its issue tracker API
releasesNoBitbucket has no release objects: read tags instead
tagsYes
branchesYes
contributorsFrom commitsBitbucket has no contributors list: commits in the date range, counted per author
pipeline_runsYesBitbucket Pipelines runs

Choosing issues or releases fails with VALIDATION_FAILED before any request is sent.

Columns left empty

ResourceEmpty columns
repositoriesarchived, stars, forks, open_issues, pushed_at
commitscommitter_name, committer_email, additions, deletions
pull_requestsclosed_at, merged_at, additions, deletions, changed_files
branchesprotected
pipeline_runsname, 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

ResponseCodeCauseWhat to do
401PROVIDER_ACCESS_DENIED, stage authThe token expired, was revoked or mistyped, the e-mail does not match an API token, or an app password was usedCreate an API token (with your account e-mail) or an access token, and choose Replace configuration
403PROVIDER_ACCESS_DENIED, stage permissionsA scope is missing. details.missingScopes names it, for example read:pullrequest:bitbucketCreate a new token with every scope above; scopes cannot be added later
404NOT_FOUNDThe repository or workspace does not exist, or the token cannot see itCheck the workspace ID and the repository name, and the token's workspace, project or repository
RedirectNOT_FOUNDThe repository moved or was renamedSelect the repository under its new name
429RATE_LIMITEDThe hourly limit is used upRetry after details.retryAt; scheduled refreshes wait by themselves
—VALIDATION_FAILEDissues or releases was chosenChoose another resource; use tags for releases

On this page