Catch. Debug. Replay.
Catch the webhook.
Sling it to localhost.
SlingHook gives Stripe, Shopify and GitHub a public URL, streams every request to your browser the moment it lands, and forwards it to the server on your laptop. When a signature fails, it tells you why.
No sign-up to try it. Create a free account to keep it, no card needed.
slinghook listen 3f1c9a2e --forward http://localhost:3000/webhooks
● Listening on endpoint 3f1c… Forwarding to http://localhost:3000/webhooks
14:02:11 POST #1234 → 200 37ms sig:valid
14:02:15 POST #1235 → 500 41ms sig:invalid
From provider to your breakpoint in one URL.
The same four steps you repeat every time you touch an integration, with no tunnel to babysit.
Paste one URL
Every endpoint gets a public URL that answers providers instantly, so they never retry because your laptop was asleep.
/c/3f1c9a2eSee it live
Headers, query, and JSON, form or XML bodies stream in as they arrive. Secrets are masked for screen sharing.
SSE · no refreshForward to localhost
The CLI connects outbound, the way stripe listen does, and resumes without dropping events.
slinghook listenFix and resend
Change your handler, then replay the exact request, or edit the body and send it once without touching the original.
X-Webhook-Replay: trueThe parts other webhook tools leave to you.
A signature debugger that explains the failure
Other tools say “invalid signature” and stop. SlingHook checks each common cause and tells you which one it is, then lets you try another secret without saving it.
- Wrong kind of secret, like an API key instead of whsec_…
- Stale or replayed timestamps
- Bodies re-encoded by your framework or cut off in transit
- ✓
Secret formatStarts with whsec_, no stray whitespace
- ✓
TimestampSigned 2s before arrival, inside the 5 min tolerance
- ✗
Body bytesBody was re-encoded after receipt. Whitespace and key order differ from what Stripe signed.
- ✓
Payload size4.1 KB, under the capture limit
Turn a captured event into code
One click gives you a typed model of the real payload, a fixture file, or a test that sends the event to your handler. Fields that only some array items have come out optional.
- TypeScript, Python TypedDict, PHP DTOs, Go structs
- Jest, Vitest, pytest and Laravel tests
export interface InvoicePaymentFailed { id: string; type: string; data: Data; } export interface DataObject { customer: string; amount_due: number; attempt_count: number; next_payment_attempt: number; paid: boolean; }
class DataObject(TypedDict): customer: str amount_due: int attempt_count: int next_payment_attempt: int paid: bool class InvoicePaymentFailed(TypedDict): id: str type: str data: Data
final readonly class DataObject { public function __construct( public string $customer, public int $amountDue, public int $attemptCount, public int $nextPaymentAttempt, public bool $paid, ) {} public static function fromArray(array $data): self { … } }
type InvoicePaymentFailed struct { ID string `json:"id"` Type string `json:"type"` Data Data `json:"data"` } type DataObject struct { Customer string `json:"customer"` AmountDue int64 `json:"amount_due"` AttemptCount int64 `json:"attempt_count"` NextPaymentAttempt int64 `json:"next_payment_attempt"` Paid bool `json:"paid"` }
test("handles invoice.payment_failed", async () => { const response = await fetch("http://localhost:3000/webhooks", { method: "POST", headers: { "content-type": "application/json", "X-Webhook-Replay": "true", }, body: payload, }); expect(response.status).toBeGreaterThanOrEqual(200); expect(response.status).toBeLessThan(300); });
Replay a whole checkout, not one event
Record a flow once, then replay it in order with its original timing as a repeatable test. See where your handler broke and whether the fix held.
-
+0.0scheckout.session.completed200
-
+0.4scustomer.subscription.created200
-
+0.9sinvoice.created200
-
+2.7sinvoice.paid500
-
+3.4spayment_intent.succeeded200
Small things that add up.
Command palette ⌘K
Jump to any endpoint or request, replay, pause the stream or switch theme from the keyboard.
Provider simulator
Fire a realistic Stripe, Shopify or GitHub event at your endpoint without leaving the app.
Custom responses
Return any status, body and delay to see how a provider reacts when your server misbehaves.
Pins and notes
Star the requests that matter so they survive clears and retention, and leave yourself a note.
Payload diff
Compare two requests side by side when a provider quietly changes its schema.
17 themes
Tokyo Night, Dracula, Nord, Ayu, SynthWave '84 and more, plus four light themes for daylight.
Free while you build. Flat when you ship.
No per-event surprises. Go over your monthly events on a paid plan and we keep catching instead of dropping your webhooks.
Free
For trying an integration this afternoon.
- 3 endpoints
- 1,000 events a month
- 24 hour history
- Live feed, replay, CLI relay
Pro
For developers who live in webhooks.
- Unlimited endpoints
- 100,000 events a month
- 30 day history, fully searchable
- Keeps catching past the limit
- Reserved URLs like /c/stripe-dev
- 1 custom domain
- Relay retries and email alerts
Team
For teams sharing endpoints and history.
- Everything in Pro
- 500,000 events a month
- 90 day history
- 3 custom domains
- 3 seats with roles, +$10 per extra seat
- One provider URL, each developer gets their own events
- Audit log
- Require 2FA or Google/GitHub sign-in
- Slack and Discord alerts
Business
For compliance, volume and SSO.
- 5M+ events
- 1 year history, up to 7 years
- 10 custom domains
- PagerDuty and webhook alerts
- SAML SSO
- PII redaction at capture
Self-hosted
Run SlingHook on your own server so payloads never leave your network. One Docker command, or PHP and MySQL by hand. The key is checked on your server.
- Team $399 /year up to 10 users
- Business $999 /year unlimited users, SAML, PII redaction
Your next webhook bug, explained.
Get a URL in ten seconds. Paste it into Stripe. Watch the first event land.
Get a URL now, no sign-up








