Request Inspector
Request
Response
Echo
Inspecting…
Waiting for server echo…
HTTP request echo — your browser sends real requests to /api/request-inspector and we reflect method, URL, args, headers, body, and origin IP. Nothing is logged for tracking.
How to use
- Open the page — a demo GET runs automatically with sample query parameters.
- Pick GET, POST, PUT, PATCH, or DELETE; edit query string and JSON body (POST/PUT/PATCH).
- Click Send request and read the echo JSON, args table, and headers table.
FAQ
What is Request Inspector?
An HTTP request echo built into this site. Your browser sends a real HTTP request to /api/request-inspector and the server echoes back method, full URL, query args, headers, parsed JSON body, and your origin IP.
How is this different from Headers Checker?
[Headers checker](/tools/headers-checker) shows five common headers only. Request Inspector echoes **everything** the server received — all headers, args, and POST JSON — like httpbin.org/get or /post.
Does it call httpbin.org?
No. Echo runs on this site's API — faster, no third-party rate limits, and your data stays on this domain.
Which HTTP methods work?
GET, POST, PUT, PATCH, and DELETE from the UI. The API also supports OPTIONS and HEAD for advanced testing via fetch.
Is my request stored?
We do not build a tracking database from echoes. The response is generated for your session and rate-limited like other network APIs.
Can I test form POST bodies?
The UI defaults to JSON. Form-urlencoded bodies are parsed into a form object when sent with the correct Content-Type via custom fetch — JSON is the primary demo path.
Introduction
Request Inspector is an HTTP request echo built into this site. Send GET or POST (plus PUT, PATCH, DELETE) from your browser and read back a structured echo: method, url, args, headers, json / data, and origin IP — useful for debugging clients, webhooks, and fetch calls.
Unlike pasting secrets into a public third-party echo service, this echo runs on your tool domain with the same origin guard and rate limits as our other network APIs.
Echo fields
| Field | Meaning |
|---|---|
| method | HTTP verb your browser used |
| url | Full request URL including query string |
| args | Parsed query parameters |
| headers | All request headers the server received |
| json | Parsed JSON body (POST/PUT/PATCH) |
| data | Raw body when not JSON |
| form | URL-encoded form fields when applicable |
| origin | Your public IP as seen by the server |
| timestamp | UTC time of the echo |
Typical workflows
- Debug fetch() — confirm query strings and Content-Type before shipping frontend code.
- Webhook shape — POST sample JSON and copy the echo for docs or ticket attachments.
- Header diff — compare GET vs POST header sets in the tables.
- Teach HTTP — safer classroom demo than sending student data to third-party echo services.
Common use cases
- API client QA — verify args and JSON match what your SDK sends.
- CORS prep — pair with CORS tester after confirming echo shape here.
- IP + headers — combine origin field with what is my public IP.
- Quick copy — use Copy JSON for Slack, Jira, or OpenAPI examples.
Best practices
- Use Send request after editing query or body — the page does not auto-send on every keystroke.
- Avoid posting secrets (tokens, passwords) even though echo stays on this domain.
- For five headline headers only, use headers checker.
- For remote URL response headers, use HTTP header checker.