API Testing That Doesn't Need a Browser.
testsprite test create --type backend plans and runs real HTTP requests against your live API — auth, dependent calls, edge cases — from your terminal or CI. No Playwright, no browser, no hand-written test scripts to keep in sync with your endpoints.
Reads the API Docs You Already Have
Save What You Broke
testsprite test rerun <testId> --output json after a backend change gives you a pass/fail against the real endpoint — not a snapshot of a mock that never changed.
Understand What You Want
Point it at your OpenAPI, Swagger, or Postman collection — or free-form docs — and it maps your endpoints into a test plan automatically.
Validate What You Have
Test plans support ordered action/assertion steps, so it can chain dependent calls — log in, then check the authenticated response — the way a real client would.
Suggest What You Need
Every failure is a failure bundle with the request, the response, a root-cause hypothesis, and a fix suggestion — no digging through logs to find out what broke.
$ testsprite test create --project prj_8f2a --type backend \
--plan-from checkout-api-plan.json --run --wait --output json
✓ POST /cart/apply-promo passed 340ms
✗ POST /orders failed 510ms
→ expected 201, got 500
→ rootCause: "promo code not revalidated server-side"
$ testsprite test failure get <testId> --out ./failures
Dependency-Aware, Not Just Endpoint-by-Endpoint
Real API flows aren't one request — they're a chain: authenticate, then fetch, then mutate. Test plans model that chain as ordered steps, so a test can depend on the result of the step before it.
Built for Backend-First Teams
No Browser Overhead
Backend tests run as pure HTTP calls — no browser to boot, no Playwright dependency, faster CI.
Structured Test Plans
testsprite test plan put versions your API test plan as JSON, reviewable in a pull request like the code it tests.
Free Community Version
Offers a free community version, making us accessible to everyone.
Batch Runs
testsprite test run --all --project <id> re-verifies your whole API surface in one command.
Trusted By Businesses Worldwide
"TestSprite offers rich test case generation, clear structure, and easy-to-read code. It also supports simple online debugging with the ability to quickly expand by generating new test cases."
"TestSprite's automation helps us reduce tons of manual work. The developers can easily catch and resolve bugs earlier in the development process."
FAQ
Does the CLI need my API spec, or can it work things out on its own?
Either. Point it at an OpenAPI, Swagger, or Postman file and it maps endpoints directly; without one, it can still plan from free-form docs or your existing code.
What does --type backend actually run?
Real HTTP requests against your live API, with dependency management — a test plan can chain an authenticate step into a fetch step into a mutate step, and each step is either an action or an assertion.
Do I need a browser or Playwright for this?
No — backend tests are pure HTTP calls. --type frontend is the Playwright-based browser path; --type backend skips it entirely.
What happens when an API test fails?
You get a failure bundle: the request, the response, a root-cause hypothesis, and a fix recommendation — pull it with testsprite test failure get <testId>.
Can I version my API test plans alongside my code?
Yes — test plans are JSON. testsprite test plan put updates one, and because it's just a file, it reviews like any other diff in a pull request.