Skip to main content
API testing overview
API Testing takes you from “here’s my API” to “here’s a regression suite I trust”. This page is the map; each phase has its own page.

​
Key Features

​
The API Testing Journey

API Discovery

How TestSprite finds your endpoints

Plan Generation & Editing

Review the plan, edit cases, add your own

Endpoint Tests

One runnable test per plan row

Integration Tests

Multi-step chains where one step’s output feeds the next
New to API testing? Start with the Quickstart, about 10 minutes from project creation to a passing suite.

​
What a Plan Covers

Plans group test cases into categories that fit your API: functional / happy path, schema validation, authorization, error handling and edge cases, boundary / load, and security probes. Not every category applies to every API. See Plan Generation & Editing for what each covers.
On a first run, keep every category selected. Once you have a baseline, prune the ones that don’t apply (for example, security probes for a strictly internal service).

​
Refining Tests in Natural Language

Edit a test’s description and click Regenerate, or ask in Chats. For example:
API testing overview
TestSprite regenerates the affected test code and re-runs it. See Managing Test Cases for every refinement path. Testing a website instead? See UI Testing. The wizard, refinement, and rerun concepts mirror this page; the tests run browser actions instead of HTTP calls.

​
Where to Go Next

API Discovery

The first phase: endpoint extraction

Auto-Auth

Stop pasting expiring tokens before every run

Data Flow

See the values each test captures and consumes