Bitbucket | Entitle
Create an app token
-
Go to the Atlassian API Tokens page and click Create API token with scopes.
-
Set your preferred name and expiration for the token, then click Next.
-
Choose Bitbucket as the API token app, then click Next.
-
Provide the token with these scopes, then click Next:
admin:workspace:bitbucket admin:repository:bitbucket read:workspace:bitbucket read:repository:bitbucket read:permission:bitbucket write:permission:bitbucket delete:permission:bitbucket -
Review your API token details. Once you have verified that everything is correct, click Create token.
-
Copy the token so you can provide it to the Entitle software when creating the integration.
-
Copy your email from the Atlassian Email page.
Jira credentials for email matching (optional)
Bitbucket does not provide user email addresses through its API. As a result, Entitle cannot automatically match Bitbucket users to identities based on email.
To enable email-based matching, configure Jira credentials. Entitle uses the Jira API to retrieve user email addresses for this purpose.
To create the API token for the key field, go to the Atlassian API Tokens page and click Create API token (not Create API token with scopes).
Example JSON{ "email": "<EMAIL>", "app_token": "<APP_TOKEN>", "jira_credentials": { "url": "https://<YOUR_SUBDOMAIN>.atlassian.net", "key": "<API_TOKEN>", "user": "[email protected]" }
Should you need to allowlist this integration, these are the IP addresses from which Entitle's service reaches the integration:
- Entitle EU (Cloud deployment)
- 34.243.199.171
- 54.216.133.226
- Entitle US (Pathfinder deployment)
- 52.45.229.219
- 54.88.235.213
- 3.224.15.134
- Entitle CA (Pathfinder deployment)
- 35.182.218.208
- 15.156.179.153
What's next?Make sure your setup is complete by testing your integration.
Updated 22 days ago