> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/webhooks/configure-a-webhook-in-github-enterprise.md).

# GitHub Enterprise

{% hint style="info" %}
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](https://na25.autorabit.com/autorabitrest/webhook/triggerSCMPushrequest)

Updated URL: [https://na25.autorabit.com/api/webhook/v2/\<OrgName>/trigger-scm-push-request](https://na25.autorabit.com/api/webhook/v2/<OrgName>/trigger-scm-push-request)

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

## Configure a Webhook in GitHub Enterprise

### A. Create a Webhook API Token from ARM

Follow these steps to create a webhook API token in ARM:

1. Log in to ARM.
2. Navigate to the **Admin** section and select **API Token**.
3. Click on **Create API Token**.

   ![API Token Creation](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FtLIrth7sX6Wpyz1xPhAb%2Fimage.png?alt=media\&token=d4189799-7e8b-4777-a7b6-8955ccb448e1)
4. Enter a **Token Name**.
5. Set **Type** to **webhook**.
6. (Optional) Provide a **Description**.
7. Click on **Create Option**.

   ![Webhook Token Configuration](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fk03HVDctqmqHIl65XrAN%2Fimage.png?alt=media\&token=f9259092-fa56-4bf6-9c90-c6317423e0c8)
8. Your new API token is now created.

### B. Create Webhook with Authentication on GitHub

Webhooks notify external services when specific events occur. To configure a webhook in GitHub:

1. Sign in to [GitHub](https://github.com/login).
2. Navigate to the desired repository.
3. Click on **Settings** in the repository's menu.

   ![Repository Settings](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FSX51MbqF2qMN8AjBbZhN%2Fimage.png?alt=media\&token=459579f9-5693-4d14-8cce-9802244f3148)
4. In the left sidebar, click on **Webhooks**.
5. Click on **Add webhook**.

   ![Add Webhook](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FeMepCpxqL69VXOLZPu1d%2Fimage.png?alt=media\&token=8091254a-f256-4358-951e-3d83899028d1)
6. In the **Payload URL** field, enter:

## Configure a Webhook in GitHub Enterprise

### A. Create a Webhook API Token from ARM

Follow these steps to create a webhook API token in ARM:

1. Log in to ARM.
2. Navigate to the **Admin** section and select **API Token**.
3. Click on **Create API Token**.

   ![API Token Creation](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FtLIrth7sX6Wpyz1xPhAb%2Fimage.png?alt=media\&token=d4189799-7e8b-4777-a7b6-8955ccb448e1)
4. Enter a **Token Name**.
5. Set **Type** to **webhook**.
6. (Optional) Provide a **Description**.
7. Click on **Create Option**.

   ![Webhook Token Configuration](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fk03HVDctqmqHIl65XrAN%2Fimage.png?alt=media\&token=f9259092-fa56-4bf6-9c90-c6317423e0c8)
8. Your new API token is now created.

### B. Create Webhook with Authentication on GitHub

Webhooks notify external services when specific events occur. To configure a webhook in GitHub:

1. Sign in to [GitHub](https://github.com/login).
2. Navigate to the desired repository.
3. Click on **Settings** in the repository's menu.

   ![Repository Settings](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FSX51MbqF2qMN8AjBbZhN%2Fimage.png?alt=media\&token=459579f9-5693-4d14-8cce-9802244f3148)
4. In the left sidebar, click on **Webhooks**.
5. Click on **Add webhook**.

   ![Add Webhook](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FeMepCpxqL69VXOLZPu1d%2Fimage.png?alt=media\&token=8091254a-f256-4358-951e-3d83899028d1)
6. In the **Payload URL** field, enter:

For example, if your instance is `https://login.autorabit.com` and your organization name is `autorabit.com`, the payload URL would be:

![Payload URL Configuration](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fmav5wzrnfxZoo6JXtYEr%2Fimage.png?alt=media\&token=8cf028f3-2b3b-4b4a-8268-d6e2d3cb3eaa)

7. In the **Secret** field, enter the API token generated from ARM.

![Secret Key Entry](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FBgxT9i9AoK8YpFAyKRPb%2Fimage.png?alt=media\&token=fb104e7a-9bc9-4e00-9344-751b62d048e5)

8. Set **Content type** to **application/json**.

![Content Type Selection](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FVWeFgaQYqTBZniqfiNJM%2Fimage.png?alt=media\&token=9c9cee6b-099d-41e0-9639-01ca626d58c1)

9. Under **Which events would you like to trigger this webhook?**, select **Just the push event**.
10. Click **Add webhook**.

![Add Webhook Confirmation](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FX7DQp8l82WOxC4OXlCjU%2Fimage.png?alt=media\&token=0e21f689-85ee-46fc-8434-0ea097640adf)

11. To trigger the webhook on pull requests, select **Let me select individual events** and check **Pull requests**.

![Pull Request Event Selection](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FFy0I3aR4ejoaEHfaOLRE%2Fimage.png?alt=media\&token=2f4082d8-174c-47a9-a547-5814a209d4f9)

12. Click **Add webhook** to save the configuration.

### Smart Commits

Smart Commits allow you to associate Git commits with ALM stories using specific patterns. For example:

To configure Smart Commits:

* Select the **Enable auto update on webhook** checkbox to reveal the required webhook URL.
* For more information on configuring webhooks in different repositories, refer to the [Webhook Setup Guide](file://product-guides/arm/arm-features/webhooks).
* You can also choose to [sync external smart commits](file://product-guides/arm/arm-features/version-control/introduction-to-version-control/version-control-repositories-summary).

![Smart Commit Configuration](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FH8oiSTm64zgMEaGm8DKc%2Fimage.png?alt=media\&token=927e6d3a-d58a-455f-9c9b-6e937fa14755)

### For Enterprise Customers

GitHub Enterprise users should raise a support ticket to <support@autorabit.com> to have their repository URL added to the `webhookurls.properties` file.

Use the following endpoints for enterprise configurations:

/api/webhook/v2//enterprise/trigger-scm-push-request

/api/webhook/v2//enterprise/sync-alm-commits


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/webhooks/configure-a-webhook-in-github-enterprise.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.