How to use the HTTP Request Builder
- Enter the method, URL, parameters and headers.
- Add a bearer token or basic auth and a JSON, form or text body.
- Copy the code for cURL, fetch, Axios, Python or HTTPie.
What does this tool do?
The builder escapes everything correctly for each language — shell quoting for cURL, JSON.stringify for fetch, json= for Python requests — and URL-encodes query parameters. The request is never sent from this page, so tokens stay in your browser.
Everything runs in your browser — nothing you paste is uploaded.
Why use it?
- Five languages.
- Auth helpers.
- Correct escaping.
Use cases
- Share a reproducible API request with a teammate.
- Turn API documentation into working code.
- Write request snippets for READMEs and tests.
A JSON POST as cURL
curl -X POST 'https://api.example.com/items' -H 'Authorization: Bearer <token>' -H 'Content-Type: application/json' -d '{"name":"Lamp"}'
Switch to fetch, Axios, Python requests or HTTPie for the same request in that language.
Common mistakes
- Pasting real tokens into shared snippets or tickets.
- Forgetting the Content-Type header for JSON bodies.
- Building query strings by hand without URL-encoding them.
Privacy
Everything you type is processed in your browser. Nothing you enter is sent to our servers or stored by us. There's no account to create and nothing to install.
Frequently asked questions
Is the request sent?
No. The page only builds the code, so your tokens stay in the browser.
Basic auth or bearer token?
Use what the API asks for. Basic auth sends a username and password; bearer tokens are API keys or OAuth tokens.
Will the cURL command work on Windows?
It uses Unix shell quoting; in PowerShell, quoting rules differ.
Content last updated . See how M2Toolkit works.