API request builder
Enter an HTTP method, absolute URL, query parameters, headers, and an optional JSON body to generate cURL and JavaScript fetch drafts in your browser without sending a request.
Inputs stay in your browser. The URL must be absolute HTTP(S). Query entries use key=value and headers use Name: value. A nonempty body must be valid JSON and is allowed only for POST, PUT, or PATCH. The tool applies shell single-quote escaping and builds a fetch init object but performs no network request.
Builds a local draft only and never sends the request.
How to use this tool
Enter an HTTP method, absolute URL, query parameters, headers, and an optional JSON body to generate cURL and JavaScript fetch drafts in your browser without sending a request.
Visually assemble REST API requests and generate clean cURL commands, fetch calls, and Python snippets. Manage query params, request headers, and authentication tokens without syntax errors.
💡 3 Quick Steps to Get Started
Pick GET, POST, PUT, or DELETE and enter the target API endpoint URL.
Configure Authorization headers, Content-Type, or JSON payload body.
Instantly copy production-ready cURL command-line scripts or JavaScript fetch code.
When it helps
Supports GET, POST, PUT, PATCH, and DELETE. Enter query parameters one per line or with &, and headers as one Name: value pair per line.
How it works
The URL must be absolute HTTP(S). Query entries use key=value and headers use Name: value. A nonempty body must be valid JSON and is allowed only for POST, PUT, or PATCH. The tool applies shell single-quote escaping and builds a fetch init object but performs no network request.
Worked example
Example: build a POST for https://api.example.com/users with Content-Type: application/json and {"name":"Ada"}, then copy the generated cURL or fetch.
Limits and data handling
A nonempty body must be valid JSON, and GET or DELETE cannot have a body, so bodies are available only for POST, PUT, and PATCH. Invalid URLs, non-HTTP(S) schemes, methods, query lines, or header lines return an error. The builder does not verify that the target API accepts the request.
It sends no request. Inputs and output stay in the current browser and are not sent to the GoGo Tools backend. Generated code contains headers and body verbatim, so use test credentials and do not paste a production token. Analytics events do not contain inputs or results.
HTTP Protocol, RESTful Architecture & cURL Request Guide
1. HTTP Protocol Anatomy and Semantic Methods (RFC 9110)
HTTP architecture encapsulates Request Lines, Headers, and optional Payloads. In RESTful paradigms, methods preserve strict semantics: GET for safe idempotent retrievals, POST for state-creating submissions, PUT for total resource replacements, and PATCH for atomic delta modifications.
2. Authentication Archetypes: Bearer, API Keys & Basic Auth
Modern cloud APIs utilize header-based authentication schemes: OAuth 2.0 Bearer JWTs in the `Authorization` header, specialized `X-API-Key` headers for rate quota management, and TLS-encrypted Basic Authentication.
3. Cross-Platform cURL Serialization
The builder transforms structured inputs into standards-compliant POSIX cURL commands with proper shell escaping, ready for immediate terminal execution or automated CI/CD pipeline integration.
Feedback
How can we improve this tool?
Send a suggestion or bug report for this tool.
FAQ
API request builder: Which methods and fields can I enter?
Use GET, POST, PUT, PATCH, or DELETE with an absolute HTTP(S) URL. Query key=value pairs may be separated by lines or &, and each header uses Name: value. URL, query, headers, and body are each limited to 100,000 characters.
API request builder: What output does it generate?
The tool adds query parameters to the URL, validates headers and JSON, then generates a shell-single-quoted cURL command and a JavaScript fetch draft with method, headers, and body.
API request builder: What JSON-body and input limits apply?
A nonempty body must be valid JSON, and GET or DELETE cannot have a body, so bodies are available only for POST, PUT, and PATCH. Invalid URLs, non-HTTP(S) schemes, methods, query lines, or header lines return an error. The builder does not verify that the target API accepts the request.
API request builder: Does it send requests or store secrets?
It sends no request. Inputs and output stay in the current browser and are not sent to the GoGo Tools backend. Generated code contains headers and body verbatim, so use test credentials and do not paste a production token. Analytics events do not contain inputs or results.
