A webhook is an HTTP callback that allows one application to send real-time data to another when a specific event occurs. Unlike polling, webhooks push data immediately. For example, Stripe sends a webhook to your server when a payment is completed, GitHub notifies you when a PR is merged, and Shopify alerts you on new orders. The webhook delivers a payload (usually JSON) via an HTTP POST request to your configured endpoint URL.

Use this Webhook Tester & Inspector tool! You can either send test requests using the Quick Test Send panel, generate sample payloads, or paste raw webhook data for inspection. The tool displays headers, parsed JSON body, query parameters, and raw HTTP data. You can also copy requests as cURL commands for debugging or replay. For production testing, consider using services like ngrok to expose your local server to the internet.

Most webhook providers use POST requests with a JSON or XML body. Some services use GET for verification checks, PUT/PATCH for updates, or DELETE for removal notifications. The HTTP method is typically consistent per event type. Always check the provider's documentation for their specific webhook implementation details, including expected headers like X-Hub-Signature (GitHub) or Stripe-Signature (Stripe).

1. Verify signatures: Most providers sign their payloads with HMAC. Validate the signature header using your secret key.
2. Use HTTPS: Always serve your webhook endpoint over HTTPS to encrypt data in transit.
3. Validate IPs: Some services publish IP ranges; restrict access to known sender IPs.
4. Implement idempotency: Track processed event IDs to avoid duplicate processing.
5. Set timeouts: Respond quickly (within a few seconds) to avoid provider retries.

Most webhooks deliver payloads in JSON format. Common structures include a top-level wrapper with event metadata (event type, timestamp, ID) and a nested data object. Examples: GitHub webhooks include action, repository, and sender fields. Stripe uses type and data.object. Shopify includes id, order_status, and line items. This tool helps you parse and understand any JSON webhook payload structure instantly.

Check logs: Use this inspector to verify the exact payload and headers received.
Verify the URL: Ensure the endpoint URL is correct and accessible.
Test locally: Use ngrok or similar tools to expose your local server.
Review response codes: Your endpoint should return 2xx status codes; 4xx/5xx may cause the provider to retry or disable the webhook.
Examine timing: Some providers expect responses within 5-10 seconds; slow processing can cause timeouts.