REST API Tester — HTTP Client in Your Browser
A lightweight alternative to desktop API clients: build a request, hit Send, and read the response — without installing anything or creating an account.
What you can do
Choose a method, enter a URL, add query parameters (appended automatically), set headers, pick an auth scheme (Bearer token, Basic, API key as a header or query parameter, or an OAuth 2.0 token) and provide a body as JSON, form URL-encoded, multipart form, XML/raw or plain text. You can also set a base URL prefix and a timeout (30 seconds by default). The response panel shows the status code, total time, size, and tabs for the body, the response headers and the raw text. The body is pretty-printed when it is JSON. A history of your last 10 requests (kept in memory only, so it is lost on refresh) lets you re-run or tweak earlier ones.
Understanding CORS
Requests are sent directly from your browser, so they are subject to the browser's same-origin policy. An API will only answer a cross-origin request if it returns Access-Control-Allow-Origin headers permitting it (most public APIs and anything you control with CORS enabled do). If a request fails with a network error while curl succeeds, CORS is almost certainly the reason — not your request. In that case, use the cURL Builder to generate a terminal command instead.
Good habits when testing APIs
Always send Accept: application/json and, for bodies, Content-Type: application/json — many 415/400 errors come from a missing content type. Check response headers for rate-limit counters (X-RateLimit-Remaining), pagination links and cache directives. Compare the reported time against your SLO; a 2-second response in a tester will be slower on a real user's connection.
How to use it
- Select the HTTP method and paste the endpoint URL.
- Add query params, headers and auth; for POST/PUT/PATCH, choose a body type and enter the body (use Format JSON to tidy a JSON body).
- Click Send and inspect status, timing, headers and the formatted body. Click an entry in the history list to reload an earlier request.
Example request
Creating a resource:
POST https://api.example.com/v1/orders
Authorization: Bearer eyJhbGciOi…
Content-Type: application/json
{
"customerId": "c_8f2a",
"items": [ { "sku": "ABC-1", "qty": 2 } ]
}
A healthy response is 201 Created with a Location header pointing at the new order and a JSON body echoing the resource. A 401 means the token is missing or expired — decode it with the JWT Decoder to check.
Common use cases
- Smoke-testing an endpoint you just deployed without opening a desktop client.
- Reproducing a bug report by replaying the exact request a front-end made.
- Exploring a third-party API's response shape before writing integration code.
- Checking authentication flows by swapping tokens and watching status codes.
Frequently asked questions
Do my requests go through SmartDevTools servers?
No. Requests are sent straight from your browser to the URL you enter. We never see your endpoints, headers or data.
Why do I get a network error but curl works?
The API does not allow cross-origin browser requests (CORS). Use the cURL Builder to run the request from a terminal, or test from a server-side client.
Can I test localhost APIs?
Yes, as long as your local server sends CORS headers allowing this origin, or you disable CORS enforcement in a development browser profile.
Is request history saved?
Only in memory for the current page (the last 10 requests, which you can switch off in Settings). It is not written to local storage, so refreshing the page clears it.