Configure a Webhook in Bitbucket

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/.

After the 25.3.9 release, the structure of the webhook payload URL was updated. Customers need to update the webhook URL in the repository settings of their remote repo. Some customers are still using the old webhook URL containing autorabitrest, which should now be replaced with api.

Example:

Old URL: https://na25.autorabit.com/autorabitrest/webhook/triggerSCMPushrequest

Updated URL: https://na25.autorabit.com/api/webhook/triggerSCMPushrequest

Unless you update the Payload URL, you might face pull request/trigger build-on-commit jobs triggering.

Create a Webhook API Token from ARM

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.

Create a Webhook with Authentication in Bitbucket

Log in to your Bitbucket account and open the repository where you want to configure the webhook.
Go to Settings and select Webhooks.
Enter the Webhook URL in the following format:

Example: https://login.autorabit.com/api/webhook/v2/autorabit.com/trigger-scm-push-request