← Back to Home

Webhook Inspector & Relay

A developer-first tool to capture, debug, and replay webhooks from services like Stripe, GitHub, or Shopify.

🔍 The Inspector

Stop guessing. See exactly what providers are sending you.

# Try it right now! Copy-paste into your terminal:
curl -X POST https://opspulse.debuggo.app/api/hooks/YOUR_UUID \
  -H "Content-Type: application/json" \
  -d '{"event": "charge.succeeded", "amount": 500}'
Pro Tip: Data appears in the dashboard in real-time via WebSockets. No refresh needed.

📡 The Relay

Killer Feature

Never lose a webhook again. OpsPulse acts as a sturdy proxy. We log the request immediately (safe backup), and then forward it to your destination.

1. Capture
We save Headers & Body
2. Log
Visible in Dashboard
3. Forward
POST to your Target

Localhost Development

⚠️ Note: OpsPulse runs in the cloud. We cannot access your localhost:3000 directly.

To relay webhooks to your local machine, use a tunnel like ngrok.

Stripe ➡️ OpsPulse ➡️ ngrok (https://xyz.ngrok.io) ➡️ localhost:3000

🔄 Replay

Backend crashed? Missed a critical payment webhook?No need to trigger a new event in Stripe.

Just click status 🔄 Replay in the dashboard. OpsPulse will resend the exact same payload and headers to your target URL.

Technical FAQ

Do you modify headers?

We strip unsafe headers like `Host` and `Content-Length` (to prevent protocol errors), but forward almost everything else, including custom Auth headers/Signatures.

What is the timeout?

We wait 10 seconds for your server to respond. If it times out, we mark the relay as failed (logs coming soon).

How long is data stored?

Payloads are kept for debugging purposes. (Policy TBD for MVP, currently stored indefinitely).

Start Inspecting