API Request Builder
API & BackendCompose method, URL, headers and body, then send or export the request.
Runs entirely in your browser — nothing is uploaded
Features
- All common verbs with editable headers, query parameters and JSON body.
- Send the request and inspect status, timing, headers and response body.
- Export the same request as cURL or fetch() code.
- Request history for the current session.
How to use the API Request Builder
- 1Pick a method and enter the endpoint URL.
- 2Add headers, query parameters and a body as needed.
- 3Send it, or export it as cURL for your terminal.
Frequently asked questions
Why did my request fail with a CORS error?
Browsers block cross-origin calls unless the target server sends permissive CORS headers. Export the request as cURL and run it from a terminal instead.
Why does my request fail with a CORS error?
Because the request is made by your browser, from this page, exactly as a script on any website would be. Unless the target server sends Access-Control-Allow-Origin headers permitting it, the browser blocks the response. That is a security feature of the web rather than a fault here, and it is why the generated fetch and curl snippets exist: run them from a terminal or your own backend, where no such restriction applies.
Is my API key or token sent anywhere other than the API?
No. The request goes straight from your browser to the address you entered, with no proxy or server of ours in between, and nothing you type is stored or logged. That is worth knowing precisely because request builders are somewhere people paste live credentials.
Why use this rather than curl directly?
For assembling the request and reading the response with headers and status laid out clearly, then exporting it once it is right. The export is the point: build it here, paste the curl or fetch into a script, and you keep the working version.