Skip to content
mailhooks.cc

Requests

Every webhook sent to your endpoint is captured and displayed in real time. Inspect headers, body, query parameters, method, and IP address for each incoming request.

Updated Nov 2026

Request list

The left panel shows captured requests sorted by time. Each entry displays the HTTP method, a short ID, relative timestamp, and provider badges when webhooks.cc can identify the sender. Emails sent to the endpoint's address appear in the same list with an EMAIL badge, and a switch above the list shows all requests, HTTP only, or email only.

  • Live mode: new requests are auto-selected as they arrive
  • Paused mode: review at your pace; a banner shows how many new requests arrived
  • Sort: toggle between newest-first and oldest-first
  • Filter: filter by HTTP method or search by path, body, or request ID
  • Provider badge: Stripe, GitHub, Shopify, Typeform, and other known providers show an icon in the list
  • Event badge: known event names like checkout.session.completed, push, or form_response appear under the request
  • Answer: the status the endpoint answered with, and the response rule that chose it, appear under the request

Request detail

Click a request to view its details. Tabs organize the data:

  • Body: auto-formatted based on content type (JSON, XML, form data, plain text)
  • Headers: all request headers in a key-value table
  • Query: parsed query string parameters
  • Raw: unformatted request body
  • Signature: verify the request's webhook signature (client-side or server-side)
  • Deliveries: each forwarding destination's tries for this request, with Redeliver (once the endpoint has destinations)

Above the tabs, beside the size and time, the request shows what the endpoint answered the sender with, such as Answered 402 (Rule: Payment failed), or Answered 200 when no rule matched. It is recorded when the request arrives, so it stays what the sender got even after the rules change. Emails, and requests captured before answers were recorded in November 2026, do not show it.

A format badge (JSON, XML, FORM, TEXT) appears above the body for quick identification. Emails open their own view with a preview, codes and links, and sender checks; see Email Capture.

Provider detection

webhooks.cc detects common webhook providers from preserved headers and, for providers like SendGrid, body shape. Detection is best-effort and does not require endpoint configuration.

{
  "method": "POST",
  "path": "/checkout",
  "detectedProvider": "stripe",
  "detectedEvent": "checkout.session.completed"
}

Use the provider badge as a quick visual cue while triaging mixed traffic on one endpoint. Use signature verification when you need an authenticity check.

Signature verification

When signature verification is configured on an endpoint, each request includes a verification status:

  • signatureVerified: true: the signature is valid (shield icon in the request list)
  • signatureVerified: false: the signature is invalid, with details in signatureError
  • signatureVerified: null: verification is not configured for this endpoint

See Dashboard Features for the full guide.

Copy as curl

Click the cURL button to copy a curl command that reproduces the captured request. Headers, method, body, and query parameters are preserved. Use this to replay the request from your terminal.

Replay

Click Replay to send the captured request to a different URL. Enter a destination URL (http or https), and the request is sent with the original method, headers, and body. Useful for testing your local or staging server.

Export

Use the Export menu next to the endpoint name to download requests as JSON or CSV. Exports include the currently visible (filtered) requests.

Share

Click Share above a request to publish a read-only copy at a link anyone can open, with credentials and signatures hidden. See Share a request.