# New fields in outgoing webhooks

**URL:** <https://discuss.bitrise.io/t/new-fields-in-outgoing-webhooks/25388>\
**Category:** Changelog\
**Tags:** website, feature-update\
**Created:** [July 10, 2025, 1:54pm UTC](https://discuss.bitrise.io/t/new-fields-in-outgoing-webhooks/25388 "2025-07-10T13:54:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeremyp](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/jeremyp/32/5490_2.png) [@jeremyp](https://discuss.bitrise.io/u/jeremyp)\
**Post date:** [July 10, 2025, 1:54pm UTC](https://discuss.bitrise.io/t/new-fields-in-outgoing-webhooks/25388/1 "2025-07-10T13:54:25Z")

</div>

We have added some extra metadata to [outgoing webhooks](https://devcenter.bitrise.io/en/connectivity/webhooks/adding-outgoing-webhooks.html#adding-outgoing-webhooks), which you can use to build more sophisticated integrations with your own systems.

The Build Events webhooks (build triggered and build finished) now contain two new fields:

| **New field** | **Field name** |
| --- | --- |
| Commit hash | `commit_hash` (inside the `git` object) |
| Build URL | `url` |

**Note:** we use the commit hash from the build trigger request payload so if it’s empty there (e.g. you are running E2E tests on the latest main branch) it will be empty in the outgoing webhook as well.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [October 8, 2025, 1:55pm UTC](https://discuss.bitrise.io/t/new-fields-in-outgoing-webhooks/25388/2 "2025-10-08T13:55:22Z")

</div>

This topic was automatically closed after 90 days. New replies are no longer allowed.