Skip to main content
Skip table of contents

Repository Level Configurations

Get started guide for Post Webhooks for Bitbucket app on the repository level.

Different repositories may have unique integration requirements with external services or applications. With repository-level configurations, you can set up specific webhooks for each repository, enabling seamless integration with repository-specific tools, services, or workflows. Different teams or individuals working on a repository can set up their webhooks to suit their needs.

Repository configurations by default overrides project and global configurations, and project configurations by default override global settings. But this parameter is configurable in the repository and project settings.


To start the Post Webhooks for Bitbucket plugin configuration on the repository level you have to add a new webhook in the Repository Settings section:

  1. Move to the Bitbucket repository where you wish to set up Post Webhooks for Bitbucket app.

  2. Navigate to the Repository settings by clicking on the “gear” button on the left sidebar.

  3. On the Workflow section find our application Post Webhooks.

  4. Click on Add webhook in the left corner and create a new configuration. After you have specified all the necessary parameters click on the Save button.

To enable the creation of multiple rules on the repository level contact your Bitbucket administrator.

Below you can find a short definition of each parameter:




the name of the configuration

Our advice is to name something meaningful to you and your team so that it can be understood later easier

Override the project and global configuration

the repository-level settings will override the project and global settings for that particular webhook


resourse where the data should be sent. Also you have to specify the HTTP method to be used when making requests to the target URL:

  • POST;

  • PUT;

  • GET.

Skip URL Validation

by enabling this parameter the app will allow you to use URLs that may not conform to the standard validation rules.

Enable Authentication

the app adds an authentication mechanism to the webhook requests, ensuring that only authorized parties can access the webhook endpoint. By enabling this option you have to specify folowing parameters:

  • Authentication type - the type of authentication to be used when sending requests to the webhook URL: Basic, Bearer or Kerberos authentication.

  • Username - corresponds to the user or service account that has the necessary permissions to access the webhook endpoint.

  • Password - correct password associated with the authentication mechanism you are using.

Enable Mutual TLS

enabling mutual TLS ensures that only trusted clients with valid and verified certificates can establish a connection with the webhook endpoint. By enabling this option you have to specify folowing parameters:

  • Path to Key Store - contains the private key and the associated certificate used for Mutual TLS authentication.

  • Path to Trust Store - contains trusted certificates used to verify the authenticity of other parties during Mutual TLS authentication.

  • Key Store Password - the password required to access the Key Store file.

  • Trust Store Password - password needed to access the Trust Store file.

Skip SSL Certificate Validation

this parameter instructs the app to skip the validation of SSL certificates, allowing the connection to be established even if the certificate cannot be verified.

Trigger Azure DevOps pipeline

allows you to specify the Azure DevOps pipeline that should be triggered when the webhook event occurs. By enabling this option additionality you have to specify folowing parameters:

Committers to ignore

the comma-separated list of Bitbucket user names that should NOT trigger an event. This is often used to ignore pushes from your continuous integration user.

Important: not display names, but usernames. For instance, jenkins-user.

From branches to consider

the comma-separated list of Bitbucket branch regular expressions that should be considered when filtering events.

For instance, release/*, tag/*, etc.

Destination branches to consider

the comma-separated list of Bitbucket branch regular expressions should be considered when filtering events for pull requests only.

From branches to ignore

the comma-separated list of Bitbucket branch regexes that should be ignored.

Destination branches to ignore

the comma-separated list of Bitbucket branch regexes that should be ignored.


Active checkbox should be enabled if this configuration is going to be used.

Skip CI

lets skip triggering events for commits/pull requests that include the [skip ci] or [ci skip] keywords in their title or description.

File path pattern

comma-separated list of file paths, only commits on these file paths will trigger the webhook.

For example, src/java/.*/src/main/resources/.*properties will trigger events only for the changes in the properties files.

Skip personal

skipping of the events from personal projects and repositories.

Repository events

allows you to specify the types of events that should trigger the webhook.

Pull request events

A table of created webhooks provides a centralized view of all webhooks configured across your Bitbucket repository. It makes it easier to manage and monitor them.

By clicking on checkboxes opposite each configuration, you can manage the selected webhooks list at once using the following actions:

  • disable;

  • enable;

  • delete.

Query string parameters support

How to use query string parameters

How to set up Azure DevOps Pipeline triggering from Bitbucket Server?

How to integrate Bitbucket Server with Jenkins Pipelines?

How to enable notifications from Bitbucket in Microsoft Teams?

How to choose an authentication type?


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.