API penetration testing
APIs carry your data with fewer checks than the screens in front of them. We test every endpoint in scope against the OWASP API Security Top 10, with tokens for each role.
Mapped to the OWASP API Security Top 10 (2023) · Report and retest included · Proposal within 1 business day
- Object level authorisation
- Function level authorisation
- Authentication and tokens
- Data exposure
- Rate limits and resource use
- Mass assignment and input
What this test answers
APIs expose your data model directly. A missing ownership check on one endpoint can expose every customer record, and it rarely shows up in a user interface test.
Platforms with public or partner APIs
Customers and integrators call your endpoints directly with their own tokens.
Mobile and single-page apps
The API behind the app is the real attack surface.
Fintech and payment teams
Partner banks and processors expect evidence that payment APIs were tested.
What we test
The areas below are covered in a typical engagement. The proposal names every host, role and limit in scope.
Object level authorisation
Changing an ID in a request to reach someone else’s record.
Function level authorisation
Calling admin or internal endpoints with a normal token.
Authentication and tokens
JWT handling, API keys, OAuth flows, expiry and revocation.
Data exposure
Responses that return more fields than the client needs.
Rate limits and resource use
Brute force, enumeration and expensive queries, including GraphQL depth.
Mass assignment and input
Writable fields that should be read only, and injection paths.
How the engagement runs
Our full methodScope
We agree assets, roles, environments, limits and the deadline, in writing.
Test
Manual testing guided by the relevant standard, with tools to speed up the search.
Validate
Every finding is confirmed by hand and chained where it leads further.
Report
Executive summary, evidence, severity and fix guidance in one report.
Retest
We verify your fixes and update the report you share with customers and auditors.
What we need from you
- API documentation
- An OpenAPI or Postman collection, or a GraphQL schema.
- Tokens per role
- Credentials for each role and tenant in scope.
- An environment
- A staging API with realistic data.
What you receive
- Executive summary
- Risk in plain language for leadership and your customer’s security team.
- Findings with evidence
- Severity, CVSS score, affected asset, proof and steps to reproduce.
- Fix guidance
- What to change, written for the engineers who will change it.
- Retest report
- An updated report after we verify your fixes.
Questions about API penetration testing
Yes. We test introspection exposure, query depth and cost, batching and authorisation on each resolver.
We can work from captured traffic of your web or mobile app, but documentation gives better coverage for the same days.
Yes, if you own them or have written permission from the owner. The proposal names every host in scope.
Related reading
Get a proposal for API penetration testing.
You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.