Real-time Inspectie | HookCheck
Real-time webhook debugging for developers
Zero-Latency Request Inspection
HookCheck streams incoming webhook payloads directly to your dashboard the millisecond they hit our edge nodes in Frankfurt and Virginia. No polling, no queue delays, no batch processing.
When a provider like Stripe, GitHub, or Shopify fires an event, our WebSocket relay pushes the raw JSON, headers, and signature verification status to your active session. Developers tracking high-frequency events—such as `payment_intent.succeeded` or `push` lifecycle hooks—can correlate timestamps down to the millisecond and replay failed payloads with a single click.
Live Request Console
The inspection panel updates continuously without page refreshes. Each incoming request is logged with its HTTP method, status code, latency, and payload schema.
Request Headers
View `X-Webhook-Signature`, `Content-Type`, and `User-Agent` fields instantly. Filter by custom headers like `X-Shopify-Shop-Domain` or `X-GitHub-Delivery`.
Payload Viewer
Syntax-highlighted JSON output with collapsible nesting. Supports up to 5MB payloads and automatically truncates binary data for safe rendering.
Response Simulator
Test your endpoint's retry logic by forcing 200, 404, or 500 responses. HookCheck forwards your simulated status back to the originating service to validate webhook resilience.
Why Real-Time Matters
Traditional webhook loggers rely on database writes and periodic UI refreshes, introducing 2–5 second delays that obscure race conditions and duplicate events.
Sub-20ms Delivery
Our in-memory relay pipeline ensures your dashboard reflects new events before the originating service even registers a 2xx response.
Signature Validation
HookCheck computes HMAC-SHA256 signatures on the fly. Green checkmarks confirm authenticity; red warnings flag mismatched secrets before your app processes the payload.
Event Deduplication
Automatically flags identical `idempotency_key` or `event_id` values across rapid-fire deliveries, preventing double-charges or redundant database writes.