Configure a Webhook in Bitbucket Enterprise
The following documentation is specific to Bitbucket Enterprise customers.
Last updated
Was this helpful?
The following documentation is specific to Bitbucket Enterprise customers.
As of 9 September 2025, app username and passwords have been deprecated as a type of authentication method. However, as of 9 June 2026, all existing app passwords will be disabled. Users are required to create API tokens and migrate this function prior to the deadline to avoid disruptions. https://support.atlassian.com/bitbucket-cloud/docs/api-tokens/
Go to Settings → Account settings (Atlassian account settings)
Go to Security → API tokens with scope
Once the API token is generated, the customer should use the Bitbucket repository URL while configuring the connection.
Example:
Repo URL: https://bitbucket.org/pavankumar_kodange/arm-test.git
Username: pavankumar_kodange
Password: (API token generated from Atlassian Account Settings → Security → API tokens with scope)
Log in to ARM.
Navigate to Admin Section > API Token.
Click Create API Token.

Enter a Token Name.
Select Type as webhook.
(Optional) Add a Description.
Click Create Option.

Your webhook API token is now created.
Log in to your Bitbucket account and open the target repository.
Go to Settings and select Webhooks.

In the webhook configuration form, use the following URL formats:
For SCM push events:
For ALM commit syncs:
Enter the webhook details and click Save.
Configure commit message patterns that associate commits with ALM stories. Example:

To configure a webhook:
Enable the auto update on webhook checkbox to display the webhook URL.
For setup in other repository types, refer to the Webhook Guide.
To integrate with external smart commit systems, see the Version Control Repositories Summary.
Last updated
Was this helpful?
Was this helpful?
https://login.autorabit.com/api/webhook/v2/<orgname>/enterprise/trigger-scm-push-requesthttps://login.autorabit.com/api/webhook/v2/<orgname>/enterprise/sync-alm-commits
