Build a request from its method, URL, query, headers and body, and read the same request as curl, fetch, axios, Python, Go, Java, C#, Dart, Ruby or PowerShell.
POST request · 1 worth checking
This request carries a credential
This request carries a credential
The value is kept exactly as you gave it, because quietly changing your input would be worse. Before the snippet goes into a repository, replace it with an environment variable — and if the token has been in a shell history or a shared document, rotate it.
curl \
https://api.example.com/v1/orders \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer REPLACE_WITH_TOKEN' \
-d '{
"customerId": "cus_123",
"items": [{ "sku": "TSHIRT-M", "qty": 2 }]
}'A generated template, not run against any endpoint. Move credentials into an environment variable before this goes into a repository.
HTTP Request Builder runs entirely on your device — nothing is uploaded, and no request is ever sent.
You’re on the Free plan. Compare plans
This builds a request and shows you the code for it. It does not send anything — there is no network call anywhere in this tool, which is why you can describe a request against a staging host, an internal service or a localhost port without that address leaving the page.
The same request is emitted for sixteen targets, and the escaping is done per language rather than once. That distinction is the whole difficulty: a double quote inside a header value needs `\"` in Go and Java, `'\''` in a POSIX shell, `\'` in PHP and Ruby, and a doubled `''` in PowerShell. A generator that escapes once and reuses the result produces code that looks right and does not compile.
Two details most generators get wrong are handled. Dart interpolates `$` inside single-quoted strings, so a `$` in your value is escaped there and left alone in Ruby, where it is not special. PowerShell does not treat a backtick as special inside single quotes, so one is left as written rather than doubled.
The body editor knows what the Content-Type implies. A JSON body is checked as you type, a form body is emitted as fields rather than a blob, and the header is set to match rather than left for you to remember.
Credentials are placeholders. `YOUR_TOKEN_HERE` is what goes into the snippet, and nothing you type in the auth fields is written into a generated example without you putting it there.
No. Nothing here makes a network call. It builds the request and shows you code for it, which is why you can safely describe a request against an internal host — the address never leaves your browser.
No, and nothing here implies it is. It is a template: it compiles and it carries your method, URL, headers and body faithfully, but your API's own requirements are yours to add.
Because each language quotes differently. A double quote needs a backslash in Go, `'\''` in a shell, and PowerShell doubles single quotes instead. Escaping once and reusing it is how generated snippets end up not compiling.
It is a placeholder by design. Generated examples get `YOUR_TOKEN_HERE` rather than a real credential, because snippets get pasted into issues, docs and chat messages.
JSON, form-encoded, multipart and raw with a type you set. The header follows the body kind, which removes the most common reason a request is rejected.