Create an access token for a repository
Access tokens for a repository are single-purpose access tokens (or passwords) with access to a single repository with limited permissions (specified at creation time). Use tokens for tasks such as scripting, CI/CD tools, and testing Bitbucket integrations or Marketplace apps while in development.
Access token expiry
If your workspace admin requires access tokens to have an expiry date within a certain date range, you will not be able to create an access token with no expiry date and will need to set an expiry date within the date range set by the workspace admin.
To create an access token for a repository:
At bitbucket.org, navigate to the target repository for the access token. This repository is the only one that the access token can access.
On the sidebar, select Repository Settings.
On the sidebar, under Security, select Access tokens.
Select Create access token.
Give the access token a name, usually related to the app or task that will use the token.
Under Expiry, select the date picker and select or input a specific date on which your access token will expire. The expiry date will need to be within the date range set by the workspace admin. Note: If a workspace admin does not require tokens to have an expiry date, the No expiry option will be available. Select the No expiry radio button to create your token with no expiry date, or you can select the Expires on radio button to set an expiry date for your token.
Select the permissions the access token needs. For detailed descriptions of each permission, see Repository-level access token permissions.
Select the Create button. The page will display the Access token created dialog.
Copy the generated token and either record or paste it into the app that requires access. The token is only displayed once and can't be retrieved later. Rather than recovering or reusing an access token for a repository, create a new token and consider revoking the old token.
Was this helpful?