basics
Getting Started with Webhooks
Create your first webhook endpoint and start capturing requests in under 30 seconds.
This guide gets you from zero to a verified, replayable webhook in under five minutes. Pick the provider you're integrating with and follow the matching path.
1. Create an Endpoint
Go to hooksense.com and click Create Endpoint. You'll get a unique webhook URL instantly — no signup required for the free tier.
https://hooksense.com/w/your-slug
Sign in (GitHub or email) to claim the endpoint, raise daily limits, and unlock features like custom slugs, HMAC verification, and team sharing.
2. Send a Test Request
Verify capture with a quick cURL before pointing a real provider at it:
curl -X POST https://hooksense.com/w/YOUR_SLUG \
-H "Content-Type: application/json" \
-d '{"event": "test", "data": {"id": 123}}'
The request shows up in your inspector immediately via WebSocket.
3. Connect Your Provider
Stripe
- Go to Stripe Dashboard → Developers → Webhooks → Add endpoint
- Endpoint URL:
https://hooksense.com/w/YOUR_SLUG - Select events (e.g.,
checkout.session.completed,invoice.paid) and save - Copy the signing secret (
whsec_...) and paste it into the HookSense endpoint's HMAC config for automatic verification
GitHub
- Repo → Settings → Webhooks → Add webhook
- Payload URL:
https://hooksense.com/w/YOUR_SLUG - Content type:
application/json - Set a secret, paste it into HookSense HMAC config (provider: GitHub), and save
Shopify
- Admin → Settings → Notifications → Webhooks → Create webhook
- URL:
https://hooksense.com/w/YOUR_SLUG, format JSON, latest API version - Copy the secret from the Webhooks page footer and add it to HookSense HMAC config
4. Inspect Every Request
Each captured request shows the full picture:
- HTTP method, status, source IP, latency
- All request headers
- Body with JSON formatting and syntax highlighting
- Query parameters and content type
- Auto-detected provider (Stripe, GitHub, Shopify, Twilio, SendGrid, Paddle, Linear, Slack)
- HMAC verification badge (Verified / Invalid) when a secret is configured
5. Forward to Localhost (Optional)
Run your handler on your machine while the public URL stays stable:
npx hooksense listen -p 3000
Every captured webhook is also forwarded to http://localhost:3000. See CLI docs for path mapping, login, and troubleshooting.
What's Next
- Replay any request to retest your handler with real payloads
- Verify signatures automatically for Stripe, GitHub, Shopify, custom
- Customize the response your endpoint returns
- Watch endpoint health with the dashboard and alerts
- Use the API to integrate HookSense into your tooling