GitHub Webhook Tester
Capture GitHub push, pull request, workflow, and release event payloads in real time — inspect X-Hub-Signature-256 and every event field.
Quick Answer
Go to requex.me, copy your endpoint URL, then add it as a webhook in your GitHub repository under Settings → Webhooks → Add webhook. GitHub will immediately send a ping event — you'll see it in Requex within seconds, including the X-Hub-Signature-256 header.
How to Test GitHub Webhooks with Requex
- 1
Get your Requex endpoint
Open requex.me — you get a unique HTTPS URL instantly. Copy it from the header at the top of the page.
- 2
Add a webhook in GitHub
Go to your repository → Settings → Webhooks → Add webhook. Paste the Requex URL as the Payload URL, set content type to
application/json, and choose which events to receive. You can also add a secret for HMAC verification. - 3
GitHub sends a ping
When you save, GitHub immediately sends a
pingevent to confirm delivery. You'll see it in Requex within seconds. If you see a green checkmark in GitHub, the endpoint is working. - 4
Trigger a real event and inspect it
Push a commit, open a PR, or run a workflow. Requex captures the full payload — the
X-GitHub-Eventheader, theX-Hub-Signature-256, delivery ID, and the complete JSON body including repository, sender, and commit details.
GitHub Webhook Events Reference
| Event | X-GitHub-Event Header | Typical Use |
|---|---|---|
| Push | push | Trigger CI, deploy preview |
| Pull Request | pull_request | Code review automation, Slack notifications |
| Workflow Run | workflow_run | Build status tracking, deploy triggers |
| Release | release | Changelog updates, package publishing |
| Issues | issues | Project management integrations |
| Star | star | Community tracking, analytics |
| Deployment | deployment | Custom deploy pipelines |
The X-Hub-Signature-256 Header
If you set a secret when configuring the GitHub webhook, every delivery will include an X-Hub-Signature-256 header — an HMAC-SHA256 hash of the payload body, prefixed with sha256=.
Requex captures and displays this header in full. To verify it in your handler, you need to compute the HMAC of req.rawBody (not the parsed JSON) using the same secret. This requires the raw body to be preserved before JSON parsing — see the Express middleware pattern on the Node.js tools comparison page.
Related Resources
Start Testing Webhooks Now
Generate your unique URL and test webhooks instantly. Free, no signup.
Open Webhook Tester →