HTTP Request & cURL Builder
Build reviewable cURL commands or portable config drafts from a JSON request definition, with repeated query parameters, headers, text or exact JSON bodies and POSIX shell quoting.
Settings
Try the example or enter your own settings.
This tool only creates a text draft. There is no Send button and no request is executed. Running the draft yourself can change data at its destination. Use synthetic inputs rather than private tokens: advertising scripts can technically access page inputs, and generated commands include all supplied values.
Using HTTP Request & cURL Builder
Build reviewable cURL commands or portable config drafts from a JSON request definition, with repeated query parameters, headers, text or exact JSON bodies and POSIX shell quoting.
- Try the editable JSON example, then set url and method. query and headers use arrays of string pairs so repeated names can be preserved.
- Add an optional body as a text string, JSON object or array. Choose POSIX command, portable cURL config or normalized JSON output and a timeout.
- Generate and inspect the URL, headers and body. Copy or download the draft, verify the destination and method, and run it manually only if intended.
Example
Try the included editable example. Add an optional body as a text string, JSON object or array. Choose POSIX command, portable cURL config or normalized JSON output and a timeout.
Questions & answers
Does this send my request?
No. It generates text locally. It never fetches the destination or runs cURL. Running a downloaded draft is a separate action on your computer.
Which shells are supported?
The command output is quoted for POSIX sh and Bash. It is not a PowerShell or cmd command. For another platform, use the cURL config output and your installed cURL binary.
Can query or header names repeat?
Yes. Use arrays of two-string pairs. Query parameters append to existing URL parameters. Repeated headers remain distinct; Host, Content-Length, Transfer-Encoding and Connection are rejected so cURL can manage them.
How are JSON bodies handled?
Object/array bodies use the existing exact-token JSON parser, preserving large numeric spellings. Content-Type application/json is added if absent. String bodies are literal text and do not get an automatic JSON content type.
Are shell-like values evaluated?
No. POSIX arguments use single-quote escaping, and config values escape quotes, backslashes and common whitespace. --data-raw prevents a body beginning @ from becoming a file read; URL globbing is disabled.
What limits and defaults apply?
Use 250,000 input characters, 100 query pairs, 50 explicit headers and 100,000 body characters. Timeout is 1–600 seconds. Only HTTP(S) URLs without credentials are accepted; fragments are removed. Redirects, retries and TLS bypass are not generated.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.
