Copyable request text. We never send the request.

When to use this — and when not to

Use it to turn a form into bash-quoted curl and an await fetch() snippet you will run yourself. Query rows merge through the URL API. Missing scheme → https://.

Do not expect this page to hit your API. We never send the request. Not multipart / FormData. Not Postman collections. Generated cURL uses bash single quotes — cmd.exe and PowerShell will mangle them.

What the builder actually emits

cURL: method, URL, -H lines, optional -d body, optional -L / -k. fetch: a JS object; duplicate header keys collapse to the last value. Credentials map to Fetch’s credentials option. -k skips TLS verify — local self-signed only.

Worked example

POST JSON to https://api.example.com/v1/items:

curl -sS -X POST 'https://api.example.com/v1/items' \
  -H 'Content-Type: application/json' \
  -d '{"name":"demo"}'

That same call in the browser is still subject to CORS. If fetch fails and curl works, configure CORS headers on the API — do not blame this form.

Mistakes people make

• Pasting bash cURL into PowerShell unchanged.
• Using -k against production.
• GET with a body and wondering why caches ignore it.

Related

CORS header generator · JWT decoder

Frequently asked questions