About this tool
When an HTTP call misbehaves, the first question is what did the client actually send? Your code builds one request in your head; the library, the browser or a proxy may send something else: a different Content-Type, a missing header, a query string encoded twice, a body that never made it. This HTTP request inspector gives you a temporary URL that records every request it receives, so you can see the real method, path, query parameters, headers and body, byte for byte.
How to inspect a request
- Click Create inspection URL above. You get a unique, temporary address.
- Use it in place of the real endpoint: in your app’s config, a form’s
action, an OAuth or payment callback, a curl command, Postman or your HTTP library. - Make the request. It appears here within a couple of seconds. Click it to see the body, every header in the order received, and the parsed query string.
Any method works (GET, POST, PUT, PATCH, DELETE and others), and so does any sub-path, so /hooks/your-id/v1/users/42?expand=orders is captured with its full path. Every request gets 200 OK with a small JSON reply. Opening the URL in a browser tab is a quick first check: you’ll see the GET request your browser sends, including its User-Agent and Accept headers.
What you can debug with it
- HTML forms. See whether a form posts
application/x-www-form-urlencodedormultipart/form-data, which fields are included, and how checkboxes and empty inputs are encoded. - HTTP client libraries. Compare what
fetch, Axios, Pythonrequestsor your mobile app send for the same call. Default headers, JSON serialisation and charset differ more than you’d expect. - Authentication headers. Check that the
Authorizationheader is present and well formed (Bearerplus a space and the token, or Basic with Base64 credentials) before blaming the server. - Callbacks and redirects. Use the URL as an OAuth redirect URI or payment return URL to see which parameters the provider appends.
- Query string encoding. Spot double encoding (
%2520instead of%20),+versus%20for spaces, and how repeated keys liketag=a&tag=bare sent. - Browser requests. The URL allows cross-origin calls, so you can send to it from JavaScript on any page and see the
Origin,RefererandSec-Fetch-*headers the browser adds.
Send a request from your code
Replace the URL with your own inspection URL, run it, and compare what arrives with what you meant to send.
await fetch('https://YOUR-INSPECTION-URL/orders?debug=1', {
method: 'POST',
headers: { 'Content-Type': 'application/json', Authorization: 'Bearer test_token' },
body: JSON.stringify({ sku: 'BK-42', qty: 2 }),
});import requests
requests.post(
"https://YOUR-INSPECTION-URL/orders",
params={"debug": 1},
json={"sku": "BK-42", "qty": 2},
headers={"Authorization": "Bearer test_token"},
)Invoke-RestMethod -Method Post -Uri "https://YOUR-INSPECTION-URL/orders?debug=1" `
-ContentType "application/json" `
-Headers @{ Authorization = "Bearer test_token" } `
-Body '{"sku":"BK-42","qty":2}'<form method="post" action="https://YOUR-INSPECTION-URL/signup">
<input name="email" value="test@example.com">
<input type="checkbox" name="newsletter" checked>
<button>Send</button>
</form>Reading the captured request
| Part | What to look for |
|---|---|
| Method and path | Did a redirect turn your POST into a GET? Is a trailing slash or path segment missing? |
| Query | Each parameter decoded, duplicates kept in order, so encoding mistakes are easy to spot. |
| Headers | Original casing and order. Check Content-Type, Content-Length, Authorization, Cookie and anything your proxy adds. |
| Body | JSON is pretty-printed; other text is shown as received. Binary bodies are kept as Base64 so nothing is lost. |
To decode what you find, paste a query string into the query string parser, a header block into the HTTP header parser, or a JSON body into the JSON formatter. To build the request in the first place, try the API request builder.
Request inspector or webhook tester?
They share the same engine. This page is set up for debugging your own clients, forms and callbacks. If you’re receiving events from Razorpay, Stripe, GitHub or Shopify and need to check signatures, the webhook tester has provider setup steps and verification code. A session started on either page carries over to the other in the same tab.
Privacy and limits
Only the browser tab that created a session can read its requests; knowing the URL lets someone send requests to it, not read them. Headers that only reveal the sender’s IP address (such as X-Forwarded-For) are dropped before storage. Sessions expire after an hour of inactivity (24 hours at most), data is kept in memory only, bodies up to 64 KB are accepted and the latest 50 requests are kept. Use test data, not real passwords, API keys or card numbers.
FAQ
What is an HTTP request inspector?
A tool that gives you a URL which records every request sent to it, so you can see the exact method, path, query string, headers and body a client produced. It is also called a request bin.
How do I see what my HTTP client is sending?
Create an inspection URL on this page and use it in place of the real endpoint in your code, form or API client. Make the request, and the full request appears here as it was received.
Does it accept GET, PUT, DELETE and other methods?
Yes. Any method and any sub-path after your session URL is captured, and each request is answered with 200 OK. The one exception is CORS preflight OPTIONS requests from browsers, which are answered automatically and not listed.
Why is my POST arriving as a GET?
Usually a redirect: many clients follow a 301 or 302 by switching to GET and dropping the body. Check that you call the final URL directly, including https and any trailing slash.
Can I send requests to it from browser JavaScript?
Yes. The URL allows cross-origin requests from any site, so fetch or XMLHttpRequest calls work. CORS preflight (OPTIONS) requests are answered automatically and are not listed; the real request that follows is.
Are request headers shown exactly as sent?
Yes, with their original casing and order. The only ones removed are headers that just carry the sender’s IP address, such as X-Forwarded-For.
Can I change the response the URL returns?
Not at the moment. Every request receives 200 OK with a short JSON body. To mock specific API responses, use the REST API mock generator.
Can other people see my requests?
No. Reading requests needs a secret token that only your browser tab holds. Sessions end when you click End or after an hour of inactivity, and nothing is written to disk.