cURL Command Builder

How this calculation works

Fill in the parts and the command is assembled with each value quoted for a POSIX shell and the whole thing broken across lines so it can be read and reviewed. The quoting is the part worth automating. Single quotes protect everything except a single quote, which cannot be escaped inside them at all — the only way out is to close the quoting, emit an escaped quote and reopen it. A JSON body containing an apostrophe is not an edge case, and getting this wrong produces a command that silently sends a truncated payload.

What the results mean

Content-Type

With a body and no Content-Type, curl defaults to form encoding. An API expecting JSON rejects a payload that looks perfectly correct, which is a confusing five minutes.

Line continuations

The backslashes keep the command readable across several lines. They are shell syntax, not part of the request.

Quoting

Values are quoted only where they need it, so simple URLs stay legible and anything containing spaces, quotes or shell characters is protected.

Credentials

Flagged when present. A command with a token in it should not reach a ticket, a pull request or a chat message.

Common problems and fixes

The API rejects my JSON body

Add a Content-Type: application/json header. Without one, the payload is sent as form data regardless of what it contains.

The command fails on Windows

The quoting is for a POSIX shell. PowerShell treats single quotes differently and has its own curl alias — use curl.exe explicitly and adjust the quoting.

My body gets truncated

Something in it broke out of the quoting. That is exactly the apostrophe case this tool handles; if you hand-edited the command afterwards, re-generate it instead.

Frequently asked questions

More in DevOps

• cURL Command ParserRead a curl command back in plain terms, and convert it to fetch or Python.