API testing for the gaps scanners can't see.
An API can hand the right data to the wrong person and still pass every automated check. We test every role against every endpoint, by hand.
What we test.
APIs fail quietly. An endpoint that returns the right data for the wrong user will pass every automated check you run. We test object- and function-level authorization across every role you have, plus rate limiting, mass assignment, and schema introspection.
01
Broken object level authorization (BOLA)
We check whether one user can fetch another user's records by changing an ID in the request.
02
Function level authorization gaps
We test whether a normal user can call endpoints meant only for admins.
03
Mass assignment and over-permissive schemas
We send extra fields to see if the API lets users change things they should not, like their own role.
04
Rate limiting and resource exhaustion
We check that the API limits how fast and how much someone can ask for, without trying to take it down.
05
Token handling, scopes, and JWT flaws
We test how tokens are made, checked and expired, and whether they can be forged or reused.
06
GraphQL introspection and query depth abuse
For GraphQL, we check what the schema gives away and whether huge queries are blocked.
What we look for first.
These are the problems that turn up again and again in this kind of system. We check for them first, then go wherever your setup leads.
Data leaks between users
Changing an ID returns someone else's data.
Admin endpoints anyone can call
Routes that check you are logged in, but not who you are.
Tokens that never die
Old tokens that still work long after logout.
Responses that say too much
Fields the app hides on screen but the API still sends.
How the test runs.
- 1
Agree on scope
We list the APIs, endpoints and user roles in scope, and pick a testing window.
- 2
Map every endpoint
We work from your docs, and find the endpoints that are not in them.
- 3
Test role by role
We call each endpoint as each role, and try to reach what that role should not.
- 4
Report and retest
Every finding comes with proof, the risk in plain English and how to fix it. With the Complete package, we test again after your fixes.
What we need from you
- API docs, an OpenAPI file or a Postman collection
- A token or test account for each role
- A test environment, or a safe time to test the real one
- A contact we can reach during testing
Getting this for an audit?
Every finding is tied to the rule it affects. See what auditors look for:
Everything your auditor will ask for.
One fixed price covers all of it.
One price, locked when you sign.
We confirm the scope with you first. After you sign, the bill never grows.
- What we test
- Website and API
- Start
- Within 1 week
- Retest
- In one price
- Surprise bills
- Never
The letter your auditor asks for.
Signed at the end of the Complete package, ready to send to whoever asked you for a pentest.
We test again until it is fixed.
With the Complete package, retests are part of the price. Not a second bill.
- Admin page open to the internetFixed
- Old software with known holesFixed
- Weak password rulesFixed
Big problems reach you the same day.
Not three weeks later in a report.
Real people do the testing.
Senior testers check every finding by hand. A scanner is where we start, not where we stop.
- OSCP
- OSCE
- GPEN
- GWAPT
- CISSP
- CISA
- CEH
- CRTO
- AWS Security
- Azure Security
A report you can actually read.
Plain English, with the fixes that matter most at the top.
API pentest questions, answered.
01Why test the API apart from the web app?
Your web app only uses part of your API. An attacker can call all of it directly, including endpoints no screen uses.
02Do you test REST, GraphQL and gRPC?
Yes, all three.
03Do you need our API docs?
They help us cover everything faster. Without them, we map the API ourselves, which takes a little longer.
04Does it cover the OWASP API Security Top 10?
Yes, by hand, plus the rules of your own API, which no checklist knows.
05How long does it take?
We can start within a week. Most tests then take one to three weeks, depending on size. If you have an audit date, tell us on the scope call and we will plan around it.
Other kinds of test.
Your proposal is 90 seconds away.
Type your website. Scope, timeline and a fixed price, in about 90 seconds. Free, and no sales call.
By getting a proposal, you agree to our Terms and Privacy Policy.
- No surprise bills
- Start within 1 week
- Retest and attestation letter in one price
Rather talk to a person? Book a call