API & Developer Testing Tools

HTTP Request Builder

Compose a raw HTTP/1.1 or HTTP/2 request message - request line, headers and body - exactly as it is sent over the wire.

Use the fields below to compose a raw HTTP request - method, HTTP version, headers, query parameters and body - and see the exact request message a client sends.

Method

URL

HTTP Version

Headers

Body

More API & Developer Testing Tools

View all 17

REST API Tester cURL Generator API Request Builder cURL to Code Converter JSON Minifier JSONPath Tester JSON Validator JSON Pointer Tester

Everything runs in your browser - no request is sent from here, this tool only builds the request representation for you to use elsewhere.

What Is an HTTP Request Builder?

An HTTP request builder helps you assemble every part of a raw HTTP request - method, headers, query string, and body - through a simple form, then converts it into a ready-to-use cURL command or fetch snippet.

Why Use This Tool?

Useful for protocol-level debugging, writing API documentation, teaching HTTP fundamentals, or quickly producing a request you can paste into a terminal or script without memorizing exact syntax.

How to Use the HTTP Request Builder

Select the HTTP method.
Enter the target URL and any query parameters.
Add the headers your request needs.
Enter a request body if the method supports one.
Copy the generated cURL command or fetch snippet.

If you already have a cURL command and want it converted into a specific programming language, use the cURL to Code Converter. If you want to actually send the request and see a live response, use the REST API Tester.

Frequently Asked Questions

The API Request Builder turns your request into cURL and JavaScript fetch() code you can run. The HTTP Request Builder shows the raw HTTP/1.1 or HTTP/2 request message itself - request line, headers and body - which is useful for learning, debugging and documentation.

Use GET to read data, POST to create, PUT to replace, PATCH to partially update and DELETE to remove. GET requests normally should not have a body.

It tells the server how to read the request body - for example application/json for JSON or application/x-www-form-urlencoded for form data. A missing or wrong Content-Type is a common cause of 400 and 415 errors.