Chain Tests

Test entire API flows,
not just endpoints

Connect endpoints in a visual graph and let responses flow automatically from one request to the next — login, create, fetch, delete, all in one chain.

REGISTER → VERIFY → PROFILE → WORKSPACE → INVITE
4 Connections 5 Endpoints
POSTAPI Unit

Register

/auth/register

Body included

Ready
verification_token
POSTAPI Unit

Verify Email

/auth/verify-email

Body included

Ready
token
PATCHAPI Unit

Setup Profile

/users/me

1 header · Body included

Ready
token
POSTAPI Unit

Create Workspace

/workspaces

1 header · Body included

Ready
workspace_id
POSTAPI Unit

Invite Members

/workspaces/invite

1 header · Body included

Ready
Press Run to execute the chain

Press Run chain to watch the onboarding flow execute step by step.

How it works

Build a chain once, run it any time — manually, on a schedule, or after each deploy.

1

Add endpoints to the graph

Drag any saved endpoint onto the canvas. Each becomes a node with its method, path, and configuration.

2

Connect them with lines

Draw a connection from one node's output port to the next. This defines the execution order and allows branching.

3

Map response fields

Select which field from the response (e.g. token, user_id, workspace_id) should be injected into the next request as a header, param, or body value.

4

Run and verify

Click Run chain. Each node executes in order, assertions are checked, and any failure stops the chain with a clear error.

Response field mapping

Pick any value from a response and bind it automatically to the next request.

POST /auth/register
response.verification_token
body: token
POST /auth/verify-email
POST /auth/verify-email
response.token
Authorization header
PATCH /users/me
PATCH /users/me
response.token
Authorization header
POST /workspaces
POST /workspaces
response.workspace_id
body: workspace_id
POST /workspaces/invite

Mappings are defined visually — no code required.

Everything you need

Chained requests

Connect endpoints in a visual graph. The output of one request automatically feeds into the next — no copy-pasting tokens or IDs.

Branching flows

One endpoint can fan out to multiple parallel branches — run two GET endpoints simultaneously off the same POST response.

Status code assertions

Each node asserts the expected HTTP status. If any step returns an unexpected code, the chain stops and alerts you immediately.

Response field mapping

Pick any field from a response — token, id, slug — and bind it to a header, query param, or body field in any downstream endpoint.

Common chain patterns

Real flows your team is already testing — now automated.

Auth → Protected route

Login first, pass the token, hit a secured endpoint

Create → Read → Delete

Full CRUD lifecycle verified end-to-end

Create → parallel reads

One create feeds multiple GET endpoints simultaneously

Multi-step checkout

Cart → Order → Payment → Confirmation in sequence

Upload → process → verify

File upload, background processing, result check

Full onboarding flow

Register → Verify → Profile → Workspace → Invite

Ready to test your full API flow?

Build your first chain in minutes. No code, no config files.

Create free account