API & Web
Tool data stays in browser
API Debugging Studio
Paste a cURL command or a HAR export and get a debugging digest — method, URL, status, and a request triage — with the parsed request, response + status playbook, and decoded JWT / issue review in the extended tabs. Runs in your browser; nothing is uploaded.
Auto-detected as you type. Ctrl+Enter to re-run.
How to use the API Debugging Studio
Paste a cURL command from your terminal or a captured HAR export from your browser's DevTools, and get a full debugging view — headers, body, JWT, a status playbook, and an issue review — entirely in your browser.
What it does
- Parses cURL commands and HAR entries into a structured debugging digest.
- Renders parsed request and response headers, query parameters, and formatted bodies (JSON/form/raw).
- Decodes JWT Bearer tokens in the Authorization header with expiry status.
- Reviews the request/response for common issues — JWT expiry, missing Content-Type, JSON/Content-Type mismatch, error status, insecure cookies.
- Shows an HTTP status playbook (likely causes and fixes) and a request triage checklist.
- Hands off to the cURL Converter for code snippets, the HAR Sanitizer for one-click secret redaction, and the OpenAPI → Postman Exporter for Postman collections.
When to use it
- You have a cURL command from a failing API call and want to see everything on one screen.
- You captured a HAR file and need to inspect one specific request/response without scanning the whole file.
- You want to inspect one call end-to-end before handing it to the HAR Sanitizer to redact.
- You want to convert a request to a Postman collection or code snippet — start here, then continue in the dedicated tool.
FAQ
- What input formats does the API Debugging Studio accept? It accepts cURL commands (paste from your terminal) and HAR files (export from Chrome or Firefox DevTools Network tab). It parses the first HAR entry by default; choose another with the HAR entry # option.
- Is my API data uploaded anywhere? No. All parsing, decoding, and analysis runs locally in your browser. Nothing is sent to a server. HAR files are read locally — the file is never uploaded.
- How do I decode a JWT from a request? Paste a cURL command that includes an Authorization Bearer header. The studio automatically decodes the JWT payload and shows expiry status in the Auth & issues tab.
- How do I redact secrets before sharing an artifact? Use the dedicated HAR Sanitizer, which redacts secrets and PII and exports sanitized packs; the Studio surfaces secret-shaped and expiry issues so you know what to redact.
- How is this different from the JWT Decoder or HAR Sanitizer? The Studio is a single-screen view for one API call end-to-end. Use the dedicated tools — JWT Decoder, HAR Sanitizer, cURL Converter — when you need deeper analysis of one specific artifact.
Runs locally in your browser. No API calls, headers, or tokens are uploaded. HAR files are read and processed entirely on your device.