Connect with Bitbucket Cloud
The integration with Bitbucket Cloud allows you to sync repositories to Venue.sh as entities.
- An organization in Venue.sh
- A role of Editor or above
- A Bitbucket account with an appropriate permission level
Creating an API token
Venue.sh connects to Bitbucket Cloud with an API token and the email of the Atlassian account that owns it.
Bitbucket Cloud no longer accepts app passwords. If your connection still uses an app password, create an API token and update the connection with it.
Bitbucket's documentation on API tokens describes the process in detail. While we endeavour to keep this document current, Bitbucket's process may have changed.
As a best practice, we recommend creating the token on a dedicated service account.
-
Go to your Atlassian account settings and sign in.
-
Click Create API token with scopes.
-
Give the token a name and choose its expiry date.
TIP: Remember, when the token expires, you will need to replace it to ensure no lapse in functionality.
-
Select Bitbucket as the app.
-
Choose the following scopes for the token:
- read:user:bitbucket
- read:workspace:bitbucket
- read:project:bitbucket
- read:repository:bitbucket
- write:repository:bitbucket
- read:pullrequest:bitbucket
- read:pipeline:bitbucket
The write scope does not include the read scope, so select both.
-
Click Create token.
-
Take note of the API token, as it cannot be retrieved once you leave the page.
When you add the connection in Venue.sh, enter the email of your Atlassian account in Atlassian account email and the token in API token.