cURL Command Generator

cURL is a command-line tool for making HTTP requests. A curl command is the whole request expressed as one line of shell: the URL, the method, any headers, and the body. Because it is plain text it is the standard way to share a reproducible API call — in documentation, in a bug report, or between a browser and a terminal. Every browser can export a network request as one, and every API vendor documents endpoints with one.

Paste the command into the import box at the top of this page and press Parse & load, then switch the output tab to Python, JS fetch, Axios or Go. The command is parsed into its parts — method, URL, query string, headers, auth and body — and each language is generated from those parts rather than by string substitution, so the JSON body arrives as a real object (a dict in Python) instead of a quoted string.

No. curl stops at the first 3xx response and prints it unless you pass -L (--location). This is the single most common reason a curl command "works" but returns an empty body: the endpoint moved and curl showed you the 301. Note that most HTTP libraries do the opposite and follow redirects automatically, so a faithful translation of a curl command without -L has to disable redirects — that is why the generated code here adds redirect: "manual", allow_redirects=False or a CheckRedirect function when you leave -L off.

Pass the body with -d and set the content type yourself: curl -X POST 'https://api.example.com/users' -H 'Content-Type: application/json' -d '{"name":"Ada"}'. curl does not infer the type — without that header it sends application/x-www-form-urlencoded and most APIs reply 400 or 415. Selecting the JSON body type on this page adds the header for you.

-d sends the body exactly as you typed it, so you have to escape it yourself. --data-urlencode percent-encodes each name=value pair for you, which is what you want for form fields containing spaces, ampersands or plus signs. -F sends a multipart/form-data body and lets curl generate the boundary; it is the only one of the three that can upload a file, using -F 'file=@/path/to/report.pdf'. Never set Content-Type by hand with -F — you will overwrite the boundary and the server will fail to parse the body.

Two reasons. First, the line continuation character: Unix shells use a trailing backslash, Windows CMD uses a caret, so a multi-line command copied from documentation breaks. Turn off "Break onto multiple lines" here to get a single-line command that runs anywhere. Second, quoting: CMD does not treat single quotes as quotes, so a JSON body wrapped in them arrives mangled. In CMD, wrap the body in double quotes and escape the inner ones; in PowerShell, prefer the one-line form or use curl.exe explicitly, since curl is an alias for Invoke-WebRequest in older versions.

Yes. Everything on this page runs in your browser — parsing, generating and copying all happen in JavaScript on your machine, with no network request and no logging. Nothing you type or paste is uploaded or stored. That said, treat any token you paste anywhere as worth rotating if you are unsure, and never commit a generated snippet with a live key in it.