Skip to content

Commit 7cba7df

Browse files
Document possible values for webhook target type
Added possible values for X-GitHub-Hook-Installation-Target-Type header.
1 parent 6cd4f82 commit 7cba7df

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

content/webhooks/webhook-events-and-payloads.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,15 @@ HTTP POST payloads that are delivered to your webhook's configured URL endpoint
4444
* `X-Hub-Signature-256`: This header is sent if the webhook is configured with a `secret`. This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`. For more information, see [AUTOTITLE](/webhooks/using-webhooks/securing-your-webhooks).
4545
* `User-Agent`: This header will always have the prefix `GitHub-Hookshot/`.
4646
* `X-GitHub-Hook-Installation-Target-Type`: The type of resource where the webhook was created.
47+
Possible values:
48+
49+
| Value | Description |
50+
| ----- | ----------- |
51+
| `repository` | Webhooks created at the repository level |
52+
| `organization` | Webhooks created at the organization level |
53+
| `app` | Webhooks created by GitHub Apps |
54+
55+
This header can be used to distinguish between repository, organization, and GitHub App webhooks without relying solely on the webhook payload.
4756
* `X-GitHub-Hook-Installation-Target-ID`: The unique identifier of the resource where the webhook was created.
4857

4958
To see what each header might look like in a webhook payload, see [Example webhook delivery](#example-webhook-delivery).

0 commit comments

Comments
 (0)