Data & Requests · LOCAL TOOL

Request Composer

Assemble a method, URL, headers, and body into a POSIX-shell cURL draft and a JavaScript fetch draft. Nothing is executed; the page never contacts the host you enter.

Runs in this page
No API call

WORKSPACEINPUT → RESULT

Your input

LOCAL

Result

Run the tool to see a result.

Your result will appear here. Input is not saved.

Browser-side processingNothing is sent to a tool API.

WHY THIS TOOL EXISTS

A focused job, not a black box.

The same inputs produce both a shell-friendly cURL command and a JavaScript fetch snippet, giving a team a concise handoff for a request they intend to run elsewhere.

How to use it

Choose the method and enter a URL.
Add one header per line and an optional body.
Review the generated draft, then copy it into a trusted environment.

TRY A WORKING EXAMPLE

Start with known input.

Load this sample into the workspace, run the tool, and compare the result shown below.

Show sample input

{
  "method": "POST",
  "url": "https://api.example.test/v1/items",
  "headers": "Accept: application/json\nContent-Type: application/json",
  "body": "{\"name\":\"sample item\"}"
}

Expected sample result from the local tool

Draft generated only · 2 header(s) · no request sent.

# Draft only; neither command has been sent.

curl --request POST --url 'https://api.example.test/v1/items' --header 'Accept: application/json' --header 'Content-Type: application/json' --data-raw '{"name":"sample item"}'

// JavaScript draft; not executed
const response = await fetch("https://api.example.test/v1/items", {
  "method": "POST",
  "headers": {
    "Accept": "application/json",
    "Content-Type": "application/json"
  },
  "body": "{\"name\":\"sample item\"}"
});

LIMITS AND INTERPRETATION

What the result cannot tell you.

Generated snippets are drafts and are not sent or validated against a server. Review secrets, shell quoting, and request safety before running them.

Inputs are processed in this page and are not written to local storage.