# HTTP request client — test APIs in the browser

> Send HTTP requests and inspect responses (status, headers, body) from your browser. Requests go to the API you choose; nothing is sent to us.

Compose and send HTTP requests — set method, headers, and body — and inspect the status, headers, and response. Requests go directly from your browser to the endpoint you target; nothing is routed through us.

Testing an API means firing requests and reading responses. A browser-based client lets you do that without installing a desktop app, with full control over method, headers, and body.

Turn a working request into code with cURL to code, and build its query string with the query string builder. Note browser CORS rules apply.

## How to

1. **Set the request.** Enter the URL, method, headers, and body.
2. **Send.** The request goes from your browser to the endpoint.
3. **Inspect.** Read the status, headers, and response body.

## FAQ

### Where do my requests go?

Directly from your browser to the URL you specify. We don't proxy or log them; the only server contacted is the API you're testing.

### Why might a request be blocked by CORS?

Browsers enforce CORS, so an API without permissive CORS headers may reject a browser request. The response/errors help you diagnose it.

### Is my request data stored?

No. The client runs in your browser and doesn't send your requests or tokens to us.


## Related tools

- [cURL to code](https://www.safepaper.app/dev/curl-to-code)
- [Query string](https://www.safepaper.app/dev/query-string)
- [JSON toolkit](https://www.safepaper.app/dev/json-toolkit)
- [WebSocket tester](https://www.safepaper.app/dev/websocket-tester)

---

Canonical HTML: https://www.safepaper.app/dev/http-client
Markdown: https://www.safepaper.app/dev/http-client.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.