Webhook Inspector
The Webhook Inspector is Hooklistener's core feature. It gives you a unique URL that captures every HTTP request sent to it, letting you inspect headers, bodies, query parameters, and metadata in real time.
How it works
- Create a debug endpoint — each endpoint gets a unique URL at
https://app.hooklistener.com/w/<slug> - Point your webhook provider at the URL — Stripe, GitHub, Shopify, or any service that sends webhooks
- Inspect captured requests — view them in the dashboard or via the CLI/API as they arrive in real time
Key features
Real-time capture
Requests appear in the dashboard instantly via WebSocket. No polling, no delays. Every HTTP method is supported (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS).
Full request details
For each captured request, Hooklistener records:
- Method and URL — the HTTP method and full request path
- Headers — all request headers
- Body — the raw request body (JSON is syntax-highlighted)
- Query parameters — parsed from the URL
- Remote address — the sender's IP address
- Timestamp — when the request was received
- Content length — size of the request body
Mock responses
Configure custom response rules to return specific status codes, headers, and bodies based on request attributes. Useful for testing how your webhook provider handles different responses.
Request forwarding
Replay captured requests to any URL. Forward them to your local development server, a staging environment, or another service for testing.
Replay cases
Save captured requests as repeatable integration cases. Replay them against local, staging, or named targets and assert on the response status or JSON body.
Request sharing
Generate shareable links for individual requests. Optionally protect them with a password and set an expiration time.
CSV export
Export captured requests to CSV for analysis in spreadsheets or data tools. Available on paid plans.
Request comparison
Compare two captured requests side by side to identify differences in headers, bodies, or other attributes. Available on paid plans.
Accessing webhooks
You can work with captured webhooks through multiple interfaces:
| Interface | Best for |
|---|---|
| Dashboard | Visual inspection, real-time monitoring |
| CLI | Local development, forwarding to localhost |
| REST API | CI/CD integration, replay cases |
| MCP Server | AI-assisted debugging |
Limits
The number of endpoints and request retention depend on your plan. See Plans & Billing for details.