Webhook test
Send a request to the URL below and watch it arrive: method, path, query, headers, body, content type and source IP, live.
Create a test endpoint
We will give you a URL. Send any HTTP request to it and the request appears here, headers and body included. Nothing is created until you press the button.
What a webhook receiver shows you
A webhook receiver answers an HTTP request and keeps a record of it. This one shows the method and the path, every header as it was sent, the query string, the body, the content type and the address the request came from, so you can compare what your code meant to send against what actually left it.
A browser writes the same facts down for every request a page made, in a HAR file rather than one row at a time. If that is what you need instead, start with how to record a HAR file, read it and share it safely.
Sending a webhook test from your own code
Point any client at the URL above: curl, an HTTP library, a payment provider's test button or a job in your build. Every method is accepted, the path after the endpoint id is recorded as it was sent, and rows appear here without reloading the page.
Webhooks carry work out of Session Replay as well as into a test endpoint. A finished bug report is posted to wherever your team already works, which is how a report becomes a Jira issue or a card your channel can triage.
Questions
You just saw everything one HTTP request carried
That is what a bug report should look like. Session Replay captures the screen, the console output, the network log and the browser details from the page where the bug happened, so nobody has to reproduce it first.