Webhooks guide
Inspect GitHub webhook deliveries without a local server
GitHub sends a ping after a repository webhook is created. A capture-enabled PNTR hostname lets you inspect that delivery and later redeliver events without keeping a tunnel process online.
Explore PNTR's online webhook testerPayload URL
https://yourname.pntr.dev/githubSetup
- 1
Create a capture endpoint
Create a PNTR subdomain with the webhook flow. Copy a URL such as https://yourname.pntr.dev/github.
- 2
Create the repository webhook
In the repository settings, open Webhooks, add a webhook, paste the PNTR URL as the Payload URL, and choose application/json.
- 3
Select only useful events
Start with the event types your application consumes. GitHub sends a ping immediately after the webhook is created.
- 4
Inspect headers and body
Open the PNTR request log. Use the GitHub event and delivery headers to identify the request, then inspect the JSON payload.
- 5
Redeliver while debugging
GitHub keeps a delivery history and supports redelivery. Use it to repeat the same payload after changing your parser or expected fields.
Before you ship
Use a high-entropy webhook secret for production handlers and verify GitHub's signature. PNTR helps you inspect the request but does not replace signature validation in your application.