API testing: guides, schema validation, tools and imports
API testing checks a service through its interface rather than its screens: the status code, the shape of the response, the values that matter, the time it took and the headers that protect it. Because an API has no layout to drift, the tests are faster and less flaky than browser tests, and a contract check catches the breaking change a UI test only notices later.
Start with the schema-validation guide if your worry is "the API changed and nothing told us"; with the studio guide if you want to send requests and assert on them; with the Postman page if you are choosing a tool. The three free tools here handle the artefacts API testers meet most: tokens, HAR captures and JSON.
What people search for
The literal queries this hub is written to answer; each leads to one of the pages below.
- api testing tool
- api schema validation
- api contract testing
- postman alternatives
- graphql testing
- jwt decoder
- har file analyzer
Do it: guides
Executed examples, limits stated.
API schema validation testing
JSON Schema and OpenAPI against a live response, with the exact errors a breaking change produces.
The API testing studio guide
Requests, chains, assertions, environments and imports.
GraphQL and gRPC testing
Queries, mutations, reflection and the limits.
How to test an LLM API key
The one API whose answers are not deterministic.
Learn: the terms
Definitions that link to the deeper page.
API contract test
The break between two systems that a unit test cannot see.
JSON Schema
The vocabulary a response shape is written in.
JWT (JSON Web Token)
Three parts, two readable, one signed.
API timing at microsecond resolution
Why the studio times from the socket, not the page.
Compare: tools
The tool decision, with the incumbent’s case first.
Postman alternatives
Who should stay on Postman, and the head-to-head.
API testing tool
What the studio does, its caps per plan and its limits.
Prove it: free tools and imports
Browser-only tools; nothing is uploaded.
JWT decoder
Header, claims, expiry and the warnings a reviewer looks for.
HAR file analyzer
Where a page’s time and bytes went.
JSON validator
The exact position of the first error.
Collection import
Postman, Bruno, Insomnia and Hoppscotch collections into the studio.
OpenAPI and cURL import, HAR to read
A spec or a command becomes requests; a HAR opens for reading, its entries are not imported yet.
Questions people ask
What should an API test assert?
The status code; the response shape against a schema; the values that carry the business meaning (a total, a state); the headers that protect the endpoint (content type, cache control, the security headers); and the time, measured from the socket. The schema check is the one most suites skip and the one that catches a quietly changed field.
What is the difference between API testing and contract testing?
An API test checks one call against what you expect today. A contract test checks that the shape consumers depend on has not changed, independently of the values: a field that became a number, a field that disappeared, a new required property. The schema-validation guide on this page shows both from one response.
Which free API testing tool should I start with?
For reading a token, the JWT decoder; for a slow page, the HAR analyzer; for a malformed body, the JSON validator. For sending requests with assertions, the studio’s Free plan includes 1,000 API calls a month for 14 days after the trial; the Postman alternatives page says honestly where Postman remains the better choice.
Try it on your own application
The Free plan asks for no card and runs for 14 days after the trial: record a flow, replay it, and read the evidence each step produced.