Creating a scoped API token
An API token acts with the Bitbucket permissions of the Atlassian account that creates it, so sign in as the account the connection should use.
Start a scoped API token
Name the token
On the Name API token screen, fill in the token details.
- Name:
StackOne Integration - Expires on: The date the token should stop working
- Click Next.

Select Bitbucket
On the Select the app screen, choose the app the token can reach.
- Select API token app: Bitbucket
- Click Next.

Select the scopes
On the Select Bitbucket scopes screen, tick every scope listed. Use Search by scope name to find each one. To receive webhook events, also tick read:webhook:bitbucket, write:webhook:bitbucket and delete:webhook:bitbucket.
- Click Next.

Create the token
On the Review your API token screen, check the name, expiry and scopes.
- Click Create token.

Copy the token
On the Copy API token screen, the token is shown only once and cannot be retrieved later.
- Click Copy.
- Copy the API token across.
- Your Email is the email address of the Atlassian account you signed in with.
- New tokens may take up to a minute to work after they’ve been created.

Find the Webhook Workspace
Only needed to receive webhook events. Your Webhook Workspace is the workspace slug in the address bar when you open the workspace in Bitbucket. The account that created the token must be an administrator of this workspace.
- Format:
https://bitbucket.org/{workspace}/ - Example: if your URL is
https://bitbucket.org/acme-dev/, your Webhook Workspace isacme-dev
Link the Account
Connect
- Click Connect.
- If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
- Once authorization is successful, you will see a confirmation popup.
Use Actions
Next Steps
Webhooks setup
Configure receiving Events for Bitbucket into StackOne.
