HTTP Request Tool

Tool Overview: HTTP Request Tool

The HTTP Request Tool lets you craft and inspect HTTP calls without leaving your browser. It is tuned for quick API smoke tests and debugging, and mirrors the interaction pattern used on other ToolMi utilities.

What Is HTTP Request Tool?

HTTP Request Tool builds and sends HTTP requests for quick API checks.

How to Use

1. Enter the URL and method.
2. Set headers, params, or body.
3. Send and review the response.

Common Use Cases

• API debugging and regression checks
• Reproduce issues quickly
• Share reproducible requests

❓ FAQ

Q1: Request failed?
A: Check URL, network, and auth.

Q2: How to set headers?
A: Add them in the headers section.

Q3: Response looks garbled?
A: Verify server encoding (UTF-8).

Highlights

• All common methods – send GET, POST, PUT, DELETE, PATCH, HEAD, or OPTIONS requests.
• Flexible request body – compose JSON with syntax highlighting, build form-data key/value pairs, or paste raw payloads.
• Header and query editors – add or remove custom headers and query parameters with inline controls.
• Live response summary – review status code badges together with latency and payload size in one glance.
• Response viewers – switch between formatted body, headers list, and raw text tabs; prettify JSON with one click.
• Clipboard helpers – copy the full request definition or the response body instantly.
• Local history – the latest 50 requests are stored in your browser so you can reload them later.

Sending Your First Request

1. Enter the endpoint URL and choose an HTTP method.
2. (Optional) Add headers or query parameters via the respective tabs.
3. For POST, PUT, or PATCH, pick a body type and fill in the content.
4. Set a custom timeout if required.
5. Press Send Request to perform the call.

The response panel will display status, elapsed time, body, and headers as soon as the request completes. Use Format JSON for readable JSON payloads, or Download Response to save the raw body as a file.

Working with Body Modes

• JSON – edit structured data with indentation; the editor preserves formatting.
• Form Data – manage key/value rows, automatically encoded into the request payload.
• Raw – paste any plain-text payload such as XML or URL-encoded strings.

Request History

A list beneath the response view records each attempt with method, URL, status, and timestamp. Click any row to repopulate the form. Choose Clear History to wipe the local cache.

Error Handling

The tool surfaces clear feedback when things go wrong:

• Timeout – shows when the server did not respond within the configured window.
• Network issues – alerts you to DNS/CORS/connection failures.
• Unknown errors – capture unexpected issues along with the internal error name.

Each failure still lands in history so you can retry after adjusting settings.

Common HTTP Headers

Add the headers you use most often directly in the Headers tab:

• Authorization – Authorization: Bearer <token> for OAuth 2.0 bearer tokens or Authorization: Basic <base64> for basic auth.
• Content-Type – Content-Type: application/json for JSON payloads, multipart/form-data for form-data uploads, or application/x-www-form-urlencoded for classic HTML forms.
• Accept – Accept: application/json to request a JSON response, or Accept: text/html for HTML.
• User-Agent – Identify the client, for example User-Agent: ToolMi-HTTP-Client.
• Cache-Control – Cache-Control: no-cache to bypass caches while debugging.
• Custom headers – prefix with X-, e.g. X-API-KEY: your-key, to send vendor-specific metadata.

Privacy Note

All requests originate directly from your browser; no request details are relayed to ToolMi servers. Credentials or tokens remain on your device. Use caution with endpoints that enforce CORS, as browser restrictions apply.