API Request Client
Send HTTP requests, build headers and params, inspect responses — your last 25 requests are saved locally.
Requests are sent directly from your browser to the URL you enter — ArrayKit doesn't proxy, see or store them. Your request history stays in this browser's local storage.
Have a curl command? Convert it with cURL to Fetch.
About API Request Client
This API client lets you build and send HTTP requests right from your browser, like a lightweight Postman. Pick a method, enter a URL, add query parameters and headers with simple key/value rows, and attach a JSON or raw body for POST, PUT, PATCH and DELETE. Send the request and inspect the full response: status code, time, size, headers and a pretty-printed body. Every request you send is saved to your last 25, stored in this browser, so you can reopen and resend it with one click. Requests go straight from your browser to the URL you enter — they are never routed through ArrayKit — so the tool is bound by the target API's CORS policy, just like any browser fetch.
Features
- All common methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
- Build query params and headers with toggleable key/value rows
- Send a JSON or raw request body; Content-Type is set for you
- See response status, time and size at a glance
- Pretty-printed JSON response and a full response-headers view
- Your last 25 requests are saved in this browser and reloadable
- Copy the response body or headers in one click
- Runs in your browser and talks directly to the endpoint
How to use the API Request Client
- Choose an HTTP method and enter the request URL.
- Add any query params, headers, or a body in the tabs below.
- Click Send to fire the request from your browser.
- Inspect the status, timing, headers and body of the response.
Example
Input
GET https://jsonplaceholder.typicode.com/todos/1
Output
200 OK · 142 ms · 83 B
{
"userId": 1,
"id": 1,
"completed": false
}
A GET request and its formatted JSON response.
Common errors & troubleshooting
- The request fails with "Failed to fetch" and no response. — Browsers can only call APIs that allow cross-origin requests. If the target API doesn't send CORS headers, the browser blocks the response — use an API with CORS enabled or call it from your own backend.
- A request to an http:// URL is blocked. — Pages served over https can't call insecure http endpoints (mixed content). Use the https version of the API.
Frequently asked questions
- What is an API client?
- An API client lets you build and send HTTP requests and inspect the responses, so you can test and debug REST APIs without writing code. This one runs in your browser.
- Does my request go through ArrayKit's servers?
- No. Each request is sent straight from your browser to the URL you enter; ArrayKit never proxies, sees or stores it. Your request history is kept only in this browser.
- Why do I get a CORS error?
- Browsers block cross-origin responses unless the target API returns the right CORS headers. That's a browser security rule — desktop tools avoid it by not being a browser. Use a CORS-enabled API or your own server.
- Are my requests saved?
- Your last 25 requests are saved in this browser's local storage so you can resend them. Clearing the history or your browser storage removes them.
- Which HTTP methods are supported?
- GET, POST, PUT, PATCH, DELETE, HEAD and OPTIONS. POST, PUT, PATCH and DELETE can carry a request body.
Related tools
All ArrayKit tools