Connect Bitbucket Cloud

Dexter reads repositories in Bitbucket Cloud to build its code catalog (Knowledge > Code) and to correlate an incident with recent changes. It only reads: it never writes to a repository.

Step 1: Create an access token

Dexter authenticates with a Bitbucket access token. It sends the token as a bearer token, so app passwords and Atlassian API tokens, which use basic authentication, do not work.

Which access token you can create depends on your Bitbucket plan:

Token Plan What Dexter can read

Workspace access token

Premium

Every repository in the workspace

Repository access token

Any plan

That one repository

  1. In Bitbucket, open the token page:

    • Workspace token: Workspace settings > Security > Access tokens.

    • Repository token: in the repository, Repository settings > Security > Access tokens.

  2. Click Create access token.

  3. Set Expiry. The default is one week, after which Dexter’s code catalog silently empties. Choose the longest date your workspace allows.

  4. Select the read scopes:

    • Workspace token: Repositories: Read and Projects: Read.

    • Repository token: Repositories: Read. Add Pull requests: Read to let Dexter see pull requests.

  5. Click Create and copy the token. Bitbucket shows it only once.

Step 2: Connect it in Dexter

  1. In Dexter, open Admin > Integrations and expand Bitbucket Cloud under Code.

  2. Enter the Workspace: its slug, or the workspace URL.

  3. Paste the Access token, and click Save.

The card reads Connected when the token can see the workspace.

Limits

  • Dexter connects to one workspace. Saving a second workspace replaces the first.

  • Dexter stores one token. With a repository access token, it reads only that repository.

  • When the token expires, the card no longer reads Connected. Create a new token and save it.