API Testing
Collection → report

Bring your collection. Leave with answers.

Cover every endpoint without writing a line of test code.

01 · Import

Import what you already have.

Import a Postman collection with its environment, an OpenAPI or Swagger file, or add endpoints by hand.

Postman
Collection + environment
Swagger URL
https://api.example.com/openapi.json
JSON
{ "openapi": "3.0.1", "paths": { … } }
Fetched automatically
  • POST/auth/login
  • GET/products
  • GET/products/{id}
  • POST/cart/items
  • Variables resolvedPlaceholders in URLs, headers and bodies are filled from your environment.
  • Credentials detectedAPI keys and Basic auth are picked up automatically, with secrets masked.
  • Every request visibleOpen any endpoint to see its method, headers and body before you test it.
02 · Assertions

Assertions written from your requirements.

Attach a test-case sheet or a requirements document, and an assertion table is generated for every endpoint.

Assertion table · from api_test_cases.xlsxGenerated
EndpointAssertionExpected
POST /auth/loginstatus200
POST /auth/loginbody.tokenis a non-empty string
GET /productsbody.items.lengthgreater than 0
POST /ordersstatus201
POST /ordersbody.totalequals cart total
  • Led by your BRDField rules, valid and invalid examples and expected messages are followed.
  • No sheet neededWithout one, the table is built from the API and the requirements alone.
  • Edits save themselvesChange any cell and it is stored with the project straight away.
03 · Run and report

Calls run in order. Failures explain themselves.

Set the run order once, run every endpoint, and read one clear report.

POST/auth/loginreturns {{token}} 200
POST/cart/itemsuses token · returns {{cart.id}} 200
POST/ordersuses token and {{cart.id}} 201
  • Automatic chainingPut the login first, and the token it returns flows into every call after it.
  • The reason, not just redEach failed assertion shows its expected value, its actual value and why.
  • Pass rate by categorySee at a glance which kinds of checks are holding and which are not.
How it works

Four steps, start to finish.

  1. 01ImportLoad your APIs into a project.
  2. 02SelectChoose the endpoints to test.
  3. 03Add casesUpload your test cases.
  4. 04RunEvery assertion is checked, call by call.
Step 01 of 04
Explore TesterEye

The rest of the platform.