API Request Client
Send GET, POST, PUT, PATCH, and DELETE requests with headers and JSON bodies. Inspect formatted responses, status, timing, and request history.
Still loading. If the tool doesn’t appear, reload this page.
About this tool
API Request Client
Send HTTP requests, inspect responses, and save request history in your browser.
API Request Client is a lightweight REST client that runs in your browser tab, with nothing to install. Pick GET, POST, PUT, PATCH, DELETE or HEAD, enter the endpoint, add header lines or a JSON body, and read the status, timing, byte size, response headers and pretty-printed JSON. The last twelve requests stay in this browser's history, with credential headers and secret-named values left out.
How to use API Request Client
- 1
Choose an HTTP method and enter the endpoint URL.
- 2
Add request headers or a JSON body when the endpoint requires them.
- 3
Send the request and inspect the response status, timing, headers, and body.
Why use API Request Client
Real browser requests
Uses the browser Fetch API to send requests directly to the endpoint.
Readable responses
JSON responses are automatically formatted for easier inspection.
Private history
Recent requests are saved only in your browser, with credential headers and secret-named values left out of the saved copy.
Frequently asked questions
Why did my request fail with a CORS error?
The target server must allow browser requests from this site. CORS is enforced by your browser and cannot be bypassed by a frontend-only tool.
Can I send JSON?
Yes. Select a method that accepts a body, add JSON in the request body editor, and the client sends it with an application/json content type.
Are credentials stored?
The saved history leaves them out where their name says what they are. Requests go from your browser straight to the endpoint, never through this tool's server. The history kept in this browser's local storage leaves out Authorization, Cookie, API-key and token header lines, any user:password in the URL, and the values of secret-named query parameters and JSON fields, such as password, pin, otp or sig. A key under another name, or written into the URL path itself as in a webhook or bot URL, is kept, so clear the history after using one. The request itself is sent as you typed it, and the client never adds this site's own cookies to it.