Inspect & Debug Webhook Payloads
Webhooks deliver real-time events from third-party services — payment processors, CI/CD platforms, communication tools, and more — but debugging them is notoriously difficult. The event fires once, often in a non-reproducible way, and you need to capture the exact payload to understand what your endpoint received. devtoolkit.sh's Webhook Trap gives you a unique, temporary endpoint URL that captures incoming HTTP requests and displays their headers, query parameters, and body in real time. Once you have the payload, paste the JSON body into the JSON Formatter to read it clearly, and use the URL Parser to inspect any URLs embedded in the payload — such as callback URLs, redirect targets, or resource links. This combination lets you understand the full structure of an incoming event without needing to deploy log statements, set up ngrok tunnels, or wait for the event to fire again. Everything runs in your browser session for the duration of your debugging work.
Generate a unique URL to capture and inspect incoming HTTP requests in real time.
Pretty-print and format JSON with proper indentation.
Break down a URL into its individual components using the browser URL API.
FAQ
- How does the Webhook Trap work?
- The tool generates a unique temporary endpoint URL. Configure your third-party service to send webhooks to that URL, then trigger the event. The incoming request — headers, body, and query parameters — appears in the tool immediately.
- Can I replay a captured webhook payload?
- Webhook Trap captures the payload so you can copy and reuse it. To replay it, copy the JSON body and use it as the request body when testing your endpoint with a tool like curl or Postman.
- Is the webhook endpoint public?
- The endpoint URL is temporary and unique to your session. While technically accessible to anyone with the URL, the random path makes it infeasible to discover. Do not use it to receive sensitive production webhooks.