Start here
Getting started
Install APITestCenter, send your first request, and run your first performance test — in about five minutes, without touching a real system.
1. Install
Download from apitestcenter.com. The page offers the right file for your computer.
| System | File | First start |
|---|---|---|
| Windows 10 / 11 | Installer (recommended) or Portable | If Windows says “Windows protected your PC”, choose More info → Run anyway. The app is new and not yet code-signed. |
| macOS (preview) | Apple Silicon or Intel .dmg | Drag it to Applications, then right-click → Open the first time. |
| Linux (preview) | AppImage or .deb | Make the AppImage executable (chmod +x), or install the .deb. |
The Windows installer and the Linux AppImage update themselves: a new version downloads in the background and asks you to restart. The portable Windows app, macOS, and the .deb tell you when a new version is out and open the download page. The Microsoft Store copy is updated by the Store. You can check any time in About (bottom of the sidebar) — see Privacy and your data.
2. Send your first request
The app has a small practice API built in — a pretend shop with products, sign-in and orders — so you can learn without testing anything that matters.
The first time, the Test API page shows a welcome card, New here? Start with something safe to test, with three choices:
- Try a simple request — fills in a request for the product list, with a check.
- Try a sign-in example — adds two saved requests to a Practice collection: Sign in, and My orders, which signs in first and uses the token.
- Take the 1-minute tour — shows where to type, how to try a request once, then test it under load.
Close the card with ×; bring it back from Help. More about the screens: Working in the app.
- On the Test API page, choose Try a simple request on the welcome card. It fills in
{{practiceApi}}/productswith a check. - Press Send (or Ctrl+Enter).
- The Response panel shows the status (
200 OK), the time it took, and the answer. The Checks badge says whether your rule — status is 2xx — passed.
{{practiceApi}} is a variable: the app fills in the practice API's address for you. You'll use the same idea for your own APIs — see Environments and variables.
The practice API
Everything it has, to try on your own. Add {{practiceApi}} in front of each path:
| Request | What it does |
|---|---|
GET /products | The list of 12 products — fast |
GET /products/{id} | One product (1 to 12); 404 for any other id |
POST /login | Sign in: send { "username": "any name", "password": "demo" }. The answer has the token at data.token. A wrong password gives 401 |
GET /orders | Your orders — needs Authorization: Bearer <token>, otherwise 401 |
POST /orders | Create an order: send { "productId": 1, "quantity": 2 } (signed in). Answers 201 with the new order, id like A-2001 — try Save values |
GET /orders/{id} | An order you created (signed in); 404 if unknown |
GET /slow?ms=300 | Answers after a delay, in milliseconds (default 300, at most 3000) |
GET /flaky | About 1 in 10 answers is a 500 — good for seeing failures in a report |
POST /upload | Send a form with files, or a file as the body: it answers with what arrived — the fields, and each file's name, type, size and SHA-256 |
GET /events | An event stream (SSE): a tick event every second, ten of them — see WebSockets and event streams |
{{practiceWs}}/ws | A WebSocket: press Connect, then every message you send comes back |
It runs inside the app on your computer, so load-test numbers describe your computer, not a real server. Orders and sign-ins are forgotten when the app closes.
3. Run your first performance test
- Open the Performance tab under the request. Leave the preset on Smoke — 2 simulated users for 30 seconds.
- Press Run performance test (Ctrl+Shift+Enter).
- Watch the live charts. When it finishes, the Performance report shows:
- a Result — looks healthy, usable with caveats, or failing — with the reasons underneath;
- key numbers — requests per second, response time (p95), failed requests;
- charts of how it went second by second.
Reading the report explains every number.
4. Try your own API
- Paste a URL — or a whole
curlcommand copied from your browser's DevTools — into the request bar. - Coming from Postman or Swagger? Use Import in the saved-requests panel. Collections, environments and OpenAPI files come in as saved requests.
- Press Ctrl+S to save a request into a collection (a folder).
Where to next
- Add rules for a correct answer: Checks.
- Sign in first and reuse the token: Chaining and test data.
- Run a whole folder of requests: Run a collection.