> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testsprite.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Overview
> AI-powered backend testing for RESTful APIs. Discover endpoints, generate plans, ship endpoint and integration tests, watch them run, and auto-clean up the data they touched.
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
| Feature | Description |
| :- | :- |
| Endpoint + Integration Tests | Per-endpoint coverage *and* multi-step chains where one test's response feeds the next |
| Dynamic Variables | Values captured from one response and injected into the next request |
| Auto Cleanup | After every run, TestSprite deletes the records your tests created |
| Auto-Auth | Configure your login flow once; TestSprite fetches a fresh token before every run |
| Smart Reports | Error types, root causes, and recommended fixes for every failure |
| Natural Language Refinement | Adjust any test in natural language, no code required |
## The API Testing Journey
```mermaid theme={null}
flowchart LR
A["1\. API Discovery
extract endpoints from
PRD, docs, and live calls"]
M["2\. Feature Map
features and use cases
on Test Coverage"]
B["3\. Plan Generation
per-endpoint plan items
with priorities"]
C["4\. Endpoint Tests
one test per endpoint
covering CRUD and edges"]
D["5\. Integration Tests
multi-step chains across
related endpoints"]
E["6\. Run"]
F["7\. Cleanup
records your tests created
get removed afterward"]
A --> M --> B --> C --> D --> E --> F
```
How TestSprite finds your endpoints
Review the plan, edit cases, add your own
One runnable test per plan row
Multi-step chains where one step's output feeds the next
New to API testing? Start with the [Quickstart](/web-portal/core/api/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](/web-portal/core/api/api-plan-gen#the-plan-structure) 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:
```text Refine theme={null}
Test POST /orders with invalid parameters and expect a 400 error code.
```
```text Add theme={null}
Add a test for the rate-limit edge — burst 100 calls in 1 second, expect at least one 429.
```
```text Edit theme={null}
For the GET /users/{id} test, drop the assertion on `created_at` — it's a timestamp and flaps.
```
TestSprite regenerates the affected test code and re-runs it. See [Managing Test Cases](/web-portal/core/working-with-test/managing-test-cases) for every refinement path.
Testing a website instead? See [UI Testing](/web-portal/core/ui/ui-testing). The wizard, refinement, and rerun concepts mirror this page; the tests run browser actions instead of HTTP calls.
## Where to Go Next
The first phase: endpoint extraction
Stop pasting expiring tokens before every run
See the values each test captures and consumes
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.