tool4.dev

HTTP & APIs / LOCAL TOOL

HTTP Request Builder

Build an HTTP request locally and generate equivalent cURL, fetch, Python, or Go code without sending it.

Runs locally — input is never uploaded
RequestChoose a method and enter a URL
Method
Query parameters
Headers
Body
Authentication
Ready when you are

WHAT IT DOES

Shape the request before you send it.

Choose an HTTP method, URL, query parameters, headers, body, and optional authentication, then generate the request in cURL, JavaScript fetch, Python requests, or Go net/http. The builder never makes the request: it turns a local description into code you can inspect before giving it to an application.

Why use it?

Use it to compose a request from separate fields when you do not already have a cURL command, then inspect the code before allowing it to contact an API.

How to use this tool

  1. Choose the method and enter the URL. Add query parameters and headers in their rows; leave unused rows empty.
  2. Select the body format the endpoint expects and enter optional authentication only when needed.
  3. Choose the output client and generate. Review Content-Type, repeated parameters, and credentials in the produced code before copying or running it.
  4. A generated request is not a successful request: this page does not send it or validate the server's response.

Details and limitations

  • Query parameters and headers are kept as separate rows, so repeated header names remain visible instead of being collapsed into an object.
  • Raw, JSON, URL-encoded, and multipart body modes describe different wire formats; the generated code names the selected mode rather than guessing from punctuation.
  • Basic and bearer credentials use masked fields and are inserted only into the generated output after you choose to generate it.
  • The output uses the same request model as the cURL converter, so a request built here and a command parsed there share method, header, body, and transport semantics.
  • This tool does not contact the URL, resolve a hostname, or store the request in the page address. It is a code-generation surface, not a browser for APIs.

COMMON QUESTIONS

Request Builder questions

Does the builder send my request?
No. Generate only writes client code into the output panel. It does not make a network request, resolve the hostname, or send the URL, headers, body, or credentials to tool4.dev.
Why are repeated headers kept as separate rows?
HTTP can carry more than one field with the same name, and collapsing those rows into a map would lose what you asked to send. The generated language decides how to represent the repeated fields and says when that representation is approximate.
Can I build a multipart upload?
Yes. Choose multipart and add fields or files in the body controls. The generated clients create the boundary and mark file handling where the target language can reproduce it.