WHAT WE LOOK AT
A valid request can still be a security problem.
An endpoint can respond exactly as designed and still expose another customer’s data. We examine the relationship between identities, objects and actions, and test the business rules that sit behind the interface.
Object & function permissions
Whether users can read or change records, or call functions, outside their role.
Authentication & tokens
How credentials and tokens are issued, checked, expired and handled across requests.
Input & responses
Unexpected input, excess data in responses and information revealed by errors.
Workflows & resource use
Business rules, request limits and the ways endpoints can interact. Any load-related testing is agreed in advance.
BEFORE WE BEGIN
Get the scope right.
Send the base URLs, API documentation or a collection of example requests, the authentication method and available user roles. We agree endpoints, environments, test data, third-party boundaries and testing limits.
We test APIs used by web and mobile applications as well as standalone services. A grey-box scope with documentation and accounts helps us cover authenticated workflows; a black-box scope answers a different question about what can be found with limited information.
WHAT YOU RECEIVE
Findings your team can work with.
A prioritised report explaining the findings, evidence, business impact and recommended remediation.
We can discuss findings with your developers or IT team while they make changes. Retesting checks whether the reported issues have been resolved; coverage and timing are agreed as part of the engagement.
- Evidence and reproduction steps
- Risk ratings with business context
- Remediation guidance and agreed retesting
COMMON QUESTIONS
A few things to know.
Do you need API documentation?
Documentation or example requests help us identify intended behaviour and make better use of the testing window. We can discuss a scope with limited documentation too.
Can API testing be part of a web or mobile test?
Yes. We agree the endpoints, roles and workflows included so there is a clear boundary between the application test and any wider API work.
