Repository navigation
Missing documentation: X-GitHub-Hook-Installation-Target-Type header values #41739
Description
Activity
i am working on this issue
@jothilakshmij Can i based on those values meanwhile?
@cx-michal-dzimitrovsky Let me look into this one. We don't deal with a lot of webhooks issues, so it will be good to find out which team currently owns that feature.
@Sharra-writes Thanks
I'm looking forward to it.Reacted by DarkMan8A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.
Reacted by DarkMan8I wait to this PR to merged
#41884@cx-michal-dzimitrovsky Please accept my apologies for the late reply here—there's been some confusion about the PR that was raised unofficially by a member of the community.
I would kindly ask that you raise this in the https://github.com/github/rest-api-description repository, as the API docs are where this information should live, via the schema, and if there's information in the schema that should be exposed then that's the right repository to raise an issue.
Again, please accept my sincere apologies for the late reply. For now I'm going to close this issue out.
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/webhooks/webhook-events-and-payloads
Specifically the section describing webhook headers.
What part(s) of the article would you like to see updated?
The documentation describes the
X-GitHub-Hook-Installation-Target-Typeheader but doesn't provide a complete list of possible values.Current documentation states:
What's missing:
integration,app, or something else?)Why this matters:
Developers need a reliable way to distinguish between repository webhooks, organization webhooks, and GitHub App webhooks. Currently, only checking for the
installationproperty in the payload is documented, but having clarity on header values would provide an alternative method.Expected outcome:
Add a table or list showing all possible values:
repository- for repository webhooks (already shown in examples)organization- for organization webhooks (if this is correct)This would help developers make informed decisions about how to identify webhook sources.
Additional information
This affects all developers implementing webhook handlers who need to distinguish between webhook types.
The header appears in API documentation examples (e.g., in /rest/apps/webhooks and /rest/repos/webhooks) but only with the value
repository. No other values are documented.