webhook-replay-debugger

Replay and debug webhook failures instantly

Built for backend teams under incident pressure

Stop spending half your sprint chasing broken webhook deliveries.

Capture the exact failing request, patch the payload, replay safely, and pinpoint root cause in minutes instead of hours.

Developers lose 3+ hours every week debugging production webhook drift.

Replay with one click after changing only the fields you need to test.

Instant Value Loop

From failure to fix in four concrete steps.

1. Route webhooks through the proxy endpoint.

2. Failed calls auto-appear in your dashboard with full context.

3. Edit JSON payload and replay immediately.

4. Use insights + response diffs to ship the fix fast.

The Problem

Webhook failures are buried in generic logs with no full payload snapshot.

Reproducing production failures requires guessing headers, body shape, and timing.

Each incident burns engineering hours and delays partner integrations.

The Solution

Capture failed webhook requests automatically via proxy endpoint.

Inspect request headers, payload, and downstream responses in one timeline.

Replay with edited JSON payloads and get immediate debugging insights.

Track replay history to document what fixed the failure.

Simple Pricing for API Teams

$15/month per developer. Unlimited failure capture, unlimited replays, and full request/response inspection.

Hosted checkout via Stripe Payment Link

After payment, redirect customers to /purchase/success?session_id={CHECKOUT_SESSION_ID}.

Buy Now - $15/mo Go To Dashboard

FAQ

How do I route failed webhooks into this tool?

Point your webhook destination to /api/webhook-proxy/[...slug]?target=https://your-api.com. The proxy forwards requests and stores only failed attempts with full request and response details.

How does replay work safely?

Every replay adds an x-webhook-replay header and logs the replay attempt separately. You can edit payload JSON before replaying and inspect the returned status, body, and headers.

How does checkout unlock access?

After successful Stripe checkout, Stripe sends a webhook to /api/stripe/webhook. Then the success page claims access by session_id and sets a signed httpOnly cookie for dashboard access.

Can I run this on Vercel with Postgres?

Yes. Set DATABASE_URL, STRIPE_WEBHOOK_SECRET, NEXT_PUBLIC_STRIPE_PAYMENT_LINK, and PAYWALL_COOKIE_SECRET. No ORM code generation is used, so deployment is straightforward.