Access Tokens

Access Tokens are linked to a repository, project, or workspace. They can be used for scripting tasks and integrating tools (such as CI/CD tools) with Bitbucket Cloud. Access Tokens are designed to be used for a single application with limited permissions, so they don't require two-step verification (2SV, also known as two-factor authentication or 2FA).

Access Tokens are tied to a repository, project, or workspace (rather than a user) and should not be shared. By sharing an Access Token, you're giving direct, authenticated access to everything that Token has permissions to do with the Bitbucket APIs (limited to the repository, project, or workspace it was created for).

Access Token features

Access Tokens have the following features:

  • They can be used to authenticate API calls.

  • They provide access that is limited to the repository, project, or workspace they were created for.

  • They have limited permissions (scopes) specified when the Access Token is created.

  • They are intended to be single-purpose, rather than reusable.

  • They are encrypted on our database and can't be viewed by anyone.

Access Token limitations

Access Tokens have the following limitations:

  • They can’t access anything outside the repository, project, or workspace they were created for.

  • They can't be used to manage workspace actions.

  • They can't be viewed or edited after they are created. They are intended to be replaced with a new Access Token rather than recovered or modified.

  • They don't expire and have no expiry date. They will stop working when they are revoked.

  • They can't be used to log in to Bitbucket at http://bitbucket.org.

Type of Access Token

There are three types of Access Token available for Bitbucket Cloud.

  • Repository Access Tokens — Provides access to a single repository with the permissions specified at the time of creation. Repository Access Tokens can be used for tasks such as managing a single repository or allowing a CI/CD tool to access the source code of a single repository in the workspace. For information on Repository Access Tokens, including creation and usage, see Repository Access Tokens.

  • Project Access Tokens (Premium feature) — Provides access to a single project and the repositories in it. The access permissions (or scopes) are specified at the time of creation. Project Access Tokens can be used for tasks such as managing or accessing the repositories in a single project. For information on Project Access Tokens, including creation and usage, see Project Access Tokens.

  • Workspace Access Tokens (Premium feature) — Provides access to a single workspace and the repositories and projects in it. The access permissions (or scopes) are specified at the time of creation. Workspace Access Tokens can be used for tasks such as managing or accessing the repositories in a single workspace or managing the workspace. For information on Workspace Access Tokens, including creation and usage, see Workspace Access Tokens.

Additional Help