Real-time Monitoring
Debug webhooks instantly without tunnels — see every incoming request as it hits your server, with zero page reloads.
Start MonitoringHow It Works
Hookly opens a persistent WebSocket connection between your browser and our edge servers. When a webhook fires — from Stripe, GitHub, Shopify, or any custom endpoint — the payload streams into your dashboard the millisecond it arrives. No polling. No refresh. No SSH tunnels.
The connection runs over WSS (WebSocket Secure) on port 443, so corporate firewalls and NAT routers never block it. Your unique Hookly URL acts as the ingress point; behind it, our relay service forwards the full request — headers, body, query string, and source IP — to the WebSocket channel open in your tab. The round-trip latency from receipt to display averages under 40 ms across our Frankfurt, Virginia, and Singapore edge nodes.
You can monitor multiple endpoints simultaneously. Each Hookly URL gets its own stream, and the dashboard multiplexes them into separate, color-coded lanes so you never confuse a Stripe charge.succeeded event with a GitHub push webhook.
What You See
The real-time panel renders each incoming request as a collapsible card showing the HTTP method, status code, timestamp, and a syntax-highlighted JSON body. Click any card to expand the full request headers, raw body, and a replay button that resends the exact same payload to a downstream URL for integration testing.
Why Teams Switch
< 40 ms from receipt to screen
WebSocket push means you see the payload before ngrok's terminal even echoes it. Critical when you're chasing a race condition in a payment callback or a delayed delivery notification.
Full request replay with one click
Every captured webhook is stored for 7 days. Re-send any payload to a staging endpoint, copy headers to clipboard, or export the entire event as a curl command for offline debugging.
Share live streams with your team
Invite teammates to your monitoring session with a read-only link. Everyone watches the same WebSocket feed — useful for pair-debugging a failing webhook during a deployment window.
Auto-reconnect with zero data loss
If your browser tab goes to sleep or the network drops, Hookly queues incoming requests for up to 5 minutes and replays them the moment the WebSocket reopens. Nothing falls through the cracks.