API & HTTP Toolkit
2 API developer utilities in one tool: a cURL-to-code converter (generates JavaScript fetch, Python requests, and Node axios from a pasted curl command) and a searchable reference of 60+ standard HTTP status codes.
- Pick a mode from the pill bar: cURL → Code Converter or HTTP Status Code Reference.
- For the converter, paste a curl command (copied straight from a browser's Network tab or an API's docs) into the textarea.
- Choose a target language from the pills — JavaScript fetch, Python requests, or Node axios — and the equivalent code appears instantly, ready to copy.
- For the status reference, type a code, name, or keyword into the filter box to instantly narrow the table of 60+ IANA-registered HTTP status codes.
All processing happens entirely in your browser. Your data never leaves your device.
Key Features
- Hand-rolled, quote-aware curl command tokenizer — handles quoted strings and common flags correctly
- Parses -X/--request, repeated -H/--header, -d/--data/--data-raw, -u/--user, and -b/--cookie
- Generates JavaScript fetch, Python requests, and Node axios code from a single curl command
- Each target language shown as its own copyable code block
- Searchable reference covering 60+ standard HTTP status codes from the IANA registry
- Color-coded category badges for 1xx–5xx classes
- Instant filtering by code, name, or description text
- 100% client-side — API commands and any embedded credentials never leave your browser
About API
Working with HTTP APIs means constantly translating between formats: a curl command from a teammate's Slack message or an API's documentation needs to become real fetch/requests/axios code in your project, and a status code coming back from a server needs to be looked up to understand exactly what it means. Both are small, frequent tasks that are easy to fumble by hand — missing a header, mis-escaping quoted JSON in a shell command, or confusing a 422 with a 400.
The cURL → Code Converter includes a hand-rolled, quote-aware command-line tokenizer that parses the flags you actually encounter day to day: -X/--request for the method, repeated -H/--header for headers, -d/--data/--data-raw for the request body, -u/--user for basic auth, and -b/--cookie. It then generates equivalent, idiomatic code in three languages — JavaScript's fetch, Python's requests library, and Node's axios — so you can go from 'here's a curl command' to working code in seconds.
The HTTP Status Code Reference is a searchable table covering every standard code from the IANA HTTP Status Code Registry across all five classes — 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, and 5xx Server Error — each with its official name, a plain-English description, and a color-coded category badge. Type a code, a name fragment, or a keyword like 'redirect' or 'rate limit' to filter instantly.
Frequently Asked Questions
-X/--request (HTTP method), repeated -H/--header (headers), -d/--data/--data-raw/--data-binary (request body), -u/--user (basic auth), -b/--cookie (cookie header), and the bare URL argument. Unrecognized boolean flags like -k or -s are safely ignored rather than breaking the parse.
No. The entire parser and code generator run as JavaScript in your browser tab — the command you paste, including any embedded API keys or auth headers, is never transmitted anywhere.
The parser needs a bare URL argument (not prefixed with a flag) to know what to request. If your command uses unusual quoting or a flag combination not listed above, simplify it or check that the URL isn't accidentally being consumed as a flag's value.
Over 60 standard codes spanning all five classes (1xx–5xx), based on the IANA HTTP Status Code Registry, including less common but real-world ones like 429 Too Many Requests, 451 Unavailable For Legal Reasons, and 507 Insufficient Storage.
401 Unauthorized means the client hasn't authenticated (or authentication failed) — the server doesn't know who you are. 403 Forbidden means the server does know who you are but you don't have permission to access that resource.