API testing for the endpoints behind your app
Most bugs users see start in the API. We test your endpoints directly, so a wrong status code, a missing permission check or a broken edge case is found before the screen ever shows it.
Pay as you go: you pay for each finding, at a rate agreed before we start.
What we check in an API
Correct responses
Status codes, response shape and values for valid requests, checked against your documentation.
Bad input
Missing fields, wrong types, very long values and unexpected characters, and whether the error is clear.
Permissions
One user cannot read or change another user's data, and signed-out requests are refused.
Business rules
Totals, limits, stock and state changes stay correct across a sequence of calls.
Edge cases
Empty lists, the last page, duplicate requests, and requests that arrive twice.
Contract changes
A new release has not removed or renamed a field your apps depend on.
How the work runs
You share the API
Documentation or a Postman collection, a test environment, and test credentials.
We test the endpoints
Each endpoint is called with valid, invalid and unauthorised requests.
You get the report
Every finding includes the exact request and response, so a developer can repeat it in seconds.
We can automate it
The same checks can become automated tests that run on every release.
Questions about this service
How is API testing priced?
It is pay as you go. You pay for each bug or improvement we find, at a rate set by its severity. We agree the rates with you before any testing starts.
Do you test GraphQL as well as REST?
Yes. The same questions apply to both: are responses correct, are errors handled, and are permissions enforced.
Will you test against production?
We prefer a test environment, because API tests create and change data. If production is the only option, we agree first which calls are safe to make.
Tell us what to test
Send a link and what worries you most. We reply with what we would look at first.
Start a project