Expose delivery_id in webhook headers or accept GUID

[kevinxu12]

Select Topic Area

Question

Body

Is there any way to have the github rest webhook apis

• take in the guid as a query param (https://github.com/orgs/community/discussions/58863)
• have the webhook headers expose the delivery_id

The webhook headers currently expose only the guid, but the github rest api requires the delivery_id

delivered headers:

"headers": {
"Accept": "/",
"User-Agent": "redacted",
"X-GitHub-Delivery": "<guid>",
"X-GitHub-Event": "redacted,
"X-GitHub-Hook-ID": "xxxx",
"X-GitHub-Hook-Installation-Target-ID": "xxxx",
"X-GitHub-Hook-Installation-Target-Type": "redacted",
"X-Hub-Signature": "redacted,
"X-Hub-Signature-256": "redacted",
"content-type": "application/json"
}

curl -L
-H "Accept: application/vnd.github+json"
-H "Authorization: Bearer "
-H "X-GitHub-Api-Version: 2022-11-28"
https://api.github.com/app/hook/deliveries/<delivery_id>

?

Related to https://github.com/orgs/community/discussions/58863 which seems to have been closed for inactivity, but answered.

The suggested approach here seems to be to iterate through all webhook deliveries for a match, and then to retry, but if we delivery 1000s of webhooks, this gets pretty unruly

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬