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 May 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.
- 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, orform_responseappear under the request
Request detail
Click a request to view its details. Five 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)
A format badge (JSON, XML, FORM, TEXT) appears above the body for quick identification.
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 insignatureErrorsignatureVerified: 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 dropdown in the URL bar to download requests as JSON or CSV. Exports include the currently visible (filtered) requests.