> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kodus.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a Webhook

> Manually create the Bitbucket webhook when automatic registration didn't happen, and pick the pull request triggers Kodus actually consumes.

Kodus usually creates the webhook automatically. If that didn't happen, follow these steps to set it up manually:

<Note>
  Webhook URLs must reach the Webhooks service (port 3332). Using the API domain only works if your reverse proxy routes `/.../webhook` paths to the webhooks service.
</Note>

1. Navigate to your Bitbucket repository

2. Click on "Repository settings" in the left sidebar

3. Select "Webhooks"

4. Click "Add webhook"

5. Time to configure your webhook:

   * **Title**: Kodus Code Review
   * **URL**: Drop in the URL where you want to receive notifications, the URL you put under `GLOBAL_BITBUCKET_CODE_MANAGEMENT_WEBHOOK` in the `.env` file
   * **Status**: Active
   * **SSL/TLS**: Check Enable SSL verification
   * **Triggers**: Select these events:
     * Pull Request
       * Created
       * Updated
       * Merged
       * Declined
       * Comment created

6. Click "Save"

And that's it! You've successfully set up a webhook to do code reviews in your Bitbucket repository.

<Note>
  Kodus only consumes Pull Request events — `created`, `updated`, `merged`, `declined`, and
  `comment created`. Repository, Issue, and build-status triggers are discarded on arrival, so
  leaving them unchecked keeps the webhook traffic down.

  On Bitbucket Data Center the equivalent events are `pr:opened`, `pr:modified`,
  `pr:reviewer:updated`, `pr:comment:added`, `pr:merged`, and `pr:declined`.
</Note>