Configure a Webhook in Bitbucket Enterprise

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/

A. Create a Webhook API Token in ARM

  1. Log in to ARM.

  2. Navigate to Admin Section > API Token.

  3. Click Create API Token.

Create API Token screen in ARM
  1. Enter a Token Name.

  2. Select Type as webhook.

  3. (Optional) Add a Description.

  4. Click Create Option.

Webhook token details input screen in ARM
  1. Your webhook API token is now created.


B. Create a Webhook with Authentication in Bitbucket

  1. Log in to your Bitbucket account and open the target repository.

  2. Go to Settings and select Webhooks.

Bitbucket Webhooks configuration section
  1. In the webhook configuration form, use the following URL formats:

    • For SCM push events:

      https://login.autorabit.com/api/webhook/v2/<orgname>/enterprise/trigger-scm-push-request
    • For ALM commit syncs:

      https://login.autorabit.com/api/webhook/v2/<orgname>/enterprise/sync-alm-commits
  2. Enter the webhook details and click Save.


Smart Commits

Configure commit message patterns that associate commits with ALM stories. Example:

Smart commit example and configuration options

To configure a webhook:

Last updated

Was this helpful?