httpclientBuild without the busywork.
Seven HTTP methods. Query parameters that stay in sync with your URL. Headers, raw bodies, and JSON formatting when you need them.
FREE · OPEN SOURCE · RUNS IN YOUR BROWSER
Send a request.
Send a request.
See the whole picture.
Test an endpoint, inspect a response, and keep moving. A free, open-source HTTP client that connects straight from your browser.
- No account
- No proxy
- Just HTTP
TRY AN EXAMPLEJSON API
GEThttps://nx.mtex.dev/status
200 OKIllustrative response
{
"status": "success",
"service": "nx.mtex.dev",
"direct_request": true
}Make your next request.
Choose an example or paste your own endpoint.
Ctrl / Cmd + Enter to send
Request
Response Ready when you are
- ms / - B
Ready to send
Your response will appear here.
Try the example above, or bring your own URL.
Direct browser request failed. This usually happens when the API doesn't allow cross-origin requests (CORS), is blocked by mixed-content security, or is offline.
Requests sent directly from your browser
THE ESSENTIALS, IN REACH
A focused tool for the whole request.
Read more than the status code.
Switch between pretty JSON, raw text, and response headers. Check elapsed time and payload size. Copy or download the result.
Take the next step with you.
Export a request as cURL, share a link for someone to review, or install the app for a dedicated workspace. Your workflow stays yours.
BEFORE YOU SEND
Good to know.
A direct connection comes with a few browser rules. Here is what happens to your requests and your data.
Your browser calls the API.
Requests use native fetch() and go directly to the target endpoint. Our server does not relay your API request, headers, body, or response.
Cookies are omitted. Browser-controlled headers cannot be overridden, and only response headers exposed by the API are visible.
The API has to let you in.
Cross-origin APIs must allow this site's origin through CORS. Some requests trigger an OPTIONS preflight that the API also needs to accept.
An HTTPS page cannot fetch an unencrypted HTTP endpoint. For blocked requests, use the editor's Direct browser request diagnostic, or export cURL to your terminal.
Recent requests stay local.
History saves recent methods and URLs in this browser. Query strings and URL credentials are removed. Request headers, bodies, and responses are not saved.
URL paths can still contain sensitive data. Use Clear in Recent requests to remove history. Your color-theme preference is also stored locally.
A link is readable by anyone.
Share links include the request URL and method. Headers and body are included only when you opt in. Query parameters remain part of the shared URL.
Review links for secrets before sharing; they may enter browser history or hosting logs. Shared requests load for review and are never sent automatically.
The workspace can come along.
Open the app to install it using your browser's install option, where supported. After its first successful service-worker installation, the app shell can open offline.
Sending requests still needs a connection. API responses and shared request URLs are not stored in the offline cache.
Built for text and JSON APIs.
Requests time out after 30 seconds. Response previews are limited to 5 MB. GET and HEAD requests omit a body; binary responses are displayed as text.
External presets use MTEX Nexus; availability and CORS depend on that service. Local status and echo presets are also available in the editor.
You control the send button. Loading this page or opening a shared request does not send a request to the API. Review your endpoint and payload before you send.