Not the same as JSON prettify
This guide covers HTTP Request: a real HTTP/HTTPS round trip with status, headers, and body. If you already have a response and only need a tree view, follow Debug API responses in the browser instead.
Methods include GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS with Params, Headers, and Body tabs. Responses show timing and size; JSON can be beautified. Import and export cURL to move commands from docs or DevTools.
Before you close the tab, save one sentence in your runbook about which step surfaced the root cause and whether a script could replace the browser chain next quarter. Short retrospectives beat perfect prose for on-call handoffs.
Where the bytes go
Send calls the site /api/v1/http-proxy endpoint. The WoDeTool server performs the outbound request and returns the result to your tab. It is not a pure browser-to-origin call and cannot reach your corporate LAN without a public URL.
The proxy blocks localhost, hostnames that resolve to private or reserved IPs, and non-http(s) schemes. Use local curl or Postman for internal APIs.
Rough limits: ~256KB request body, ~1MB response body (truncation flagged). The proxy route is rate-limited—see current deployment settings.
Before you close the tab, save one sentence in your runbook about which step surfaced the root cause and whether a script could replace the browser chain next quarter. Short retrospectives beat perfect prose for on-call handoffs.
Start from cURL
Paste Chrome “Copy as cURL” or a runbook command into Import cURL, then Apply. The UI splits method, URL, query, headers, and body. Accept-Encoding is dropped on import so the proxy can decompress and show a readable body.
The default sample targets https://httpbin.org/get—send once to verify the path, then swap in your staging host. URLs without a scheme are treated as https.
Before you close the tab, save one sentence in your runbook about which step surfaced the root cause and whether a script could replace the browser chain next quarter. Short retrospectives beat perfect prose for on-call handoffs.
End-to-end workflow (diagram)
Hands-on order: public staging → import cURL → adjust Authorization (sanitized) → send → on 2xx copy body to JSON Formatter; on 4xx cross-check HTTP Status Codes and response headers.
For long query strings, parse the full URL in URL Parser before editing rows in the Params tab.
Before you close the tab, save one sentence in your runbook about which step surfaced the root cause and whether a script could replace the browser chain next quarter. Short retrospectives beat perfect prose for on-call handoffs.
Failures and limits
401/403 usually means auth—decode JWT expiry per decode-jwt-check-expiry. Do not archive refresh tokens in screenshots.
When the UI marks the body truncated, fetch smaller pages from the server logs instead of treating the preview as complete.
Before you close the tab, save one sentence in your runbook about which step surfaced the root cause and whether a script could replace the browser chain next quarter. Short retrospectives beat perfect prose for on-call handoffs.
FAQ
Office-only API over VPN: The proxy still blocks private or reserved IPs and localhost—use local curl or Postman on VPN.
Empty body after cURL import: Import should strip Accept-Encoding so the proxy can decompress into a readable body.
Versus Postman environments: No env files here—edit URL, Params, and headers directly.
429 or too many requests: You hit /http-proxy rate limits; wait or shrink payloads—do not load-test production here.
Before you close the tab, save one sentence in your runbook about which step surfaced the root cause and whether a script could replace the browser chain next quarter. Short retrospectives beat perfect prose for on-call handoffs.
Worked example (step by step)
1. DevTools cURL: curl 'https://staging.example.com/api/v1/health' -H 'Authorization: Bearer eyJ...'
2. Open HTTP Request → Import cURL → Apply.
3. Verify GET and URL https://staging.example.com/api/v1/health with Authorization enabled.
4. Send; expect 200 with timing and size in the status row.
5. Beautify JSON or copy into JSON Formatter.
6. On 401, check JWT exp per decode-jwt-check-expiry, refresh staging token, resend.
7. On 502, export cURL for backend and read HTTP Status Codes.
8. Parse the next GET /search?q=... URL with URL Parser before editing Params.
Before you close the tab, save one sentence in your runbook about which step surfaced the root cause and whether a script could replace the browser chain next quarter. Short retrospectives beat perfect prose for on-call handoffs.