REST API testing
Every in-scope endpoint, method and parameter: path, query, header and JSON body. Versioned and legacy endpoints that are still reachable.
CoverageAPI Security Testing
Your API is the real perimeter. Web front ends, mobile apps, partners and AI agents all talk to it directly — and attackers skip the UI entirely. We assess your REST APIs endpoint by endpoint, role by role, to find the authorization and data exposure flaws that put customer data at risk.
Why it matters
A web or mobile interface only shows users what you intend. The API behind it often returns extra fields, accepts parameters the UI never sends and trusts that object IDs come from legitimate screens. Attackers call APIs directly with tools like curl and Burp Suite, so those assumptions do not hold.
API flaws are also hard to see from the outside. A request that returns another customer's record looks like perfectly normal traffic. Finding these issues requires systematically testing each endpoint against each role — exactly the kind of structured, repetitive work where AI-assisted workflows add speed and human review adds accuracy.
Changing one ID in a request can expose another customer's data when object-level authorization is missing.
Admin-only endpoints that are hidden in the UI but callable by ordinary users are a common and serious finding.
Missing rate limits enable credential stuffing, enumeration, scraping and expensive operations at scale.
What we test
Every in-scope endpoint, method and parameter: path, query, header and JSON body. Versioned and legacy endpoints that are still reachable.
CoverageAPI keys, OAuth 2.0 flows and JWTs: signature validation, algorithm confusion, expiry, token leakage, refresh token handling and weak credential flows.
API2:2023Systematic cross-account testing of every endpoint that takes an object identifier, including nested and bulk operations.
API1:2023Calling administrative or privileged functions with lower-privileged tokens, and switching HTTP methods to bypass checks.
API5:2023Responses that return sensitive fields — internal IDs, emails, hashes, tokens — that the client never displays but an attacker can read.
API3:2023Login, OTP, password reset and search endpoints tested for throttling. Pagination limits and expensive queries that could be abused.
API4:2023Injection into SQL/NoSQL queries, type confusion, oversized payloads, unexpected content types and server-side request forgery through URL parameters.
API7 / InjectionSubmitting extra properties such as role, isAdmin, tenantId or price to see whether the API binds fields it should reject.
API3:2023Abuse of sensitive business flows: repeating one-time actions, skipping states, racing concurrent requests and bypassing limits.
API6:2023CORS policy, verbose errors, missing security headers, exposed documentation or debug endpoints, and forgotten non-production hosts.
API8 / API9:2023Coverage depends on scope. Not every category applies to every application. The areas tested in your engagement are agreed during scoping, based on your architecture, features, user roles and the access you provide.
Standards
Our API testing uses the OWASP API Security Top 10 (2023) as a methodological reference, so every major risk class is considered and findings are mapped to categories your engineering team and customers recognise. Where your API has risks outside the list, we test those too.
OWASP projects are community methodology references. Using them does not imply certification, endorsement or compliance with any standard.
Automated & AI-assisted
Used to accelerate discovery. Output is treated as leads, never as findings.
Manual verification
Required before anything is reported as a confirmed vulnerability.
How we work
Agree base URLs, API versions, documentation, roles, test tenants, rate-limit tolerances and exclusions.
Build an endpoint inventory from documentation and live traffic, noting which take object IDs or perform privileged actions.
Run AI-assisted discovery, then manually test authentication, authorization, data exposure, input handling and logic.
Reproduce each issue with clean requests, confirm impact and remove false positives.
Deliver findings with ready-to-run reproduction requests, then verify your fixes.
Deliverables
The overall security posture of your API in business terms, with key risks and recommended priorities.
Each finding includes the exact HTTP requests and responses (or curl commands) so developers can reproduce and confirm the fix.
CVSS-based severity, OWASP API Top 10 and CWE references, and a clear statement of what an attacker could achieve.
Concrete remediation — e.g. centralised authorization checks, response allow-listing, schema validation — tailored to your stack.
FAQ
Ideally: API documentation (OpenAPI/Swagger, Postman collection or GraphQL schema), a non-production environment, and at least two test accounts per role so we can test cross-account access. We can also work from traffic captured through your web or mobile app.
Our core focus is REST APIs. GraphQL endpoints can be included where agreed during scoping — the same authorization and data exposure principles apply, with additional checks for introspection and query complexity.
Yes. We can test the backend API that a mobile app uses, either from documentation or by capturing app traffic. Testing of the mobile app binary itself is a separate activity and would be scoped separately.
Rate-limit checks are performed with controlled request volumes agreed in advance. We do not perform denial-of-service testing unless it is explicitly requested and scoped with safeguards.
Scanners can find some technical issues, but they cannot reliably tell whether user A should be able to read object 42. We test authorization with real accounts and manually confirm every reported issue.
Yes, and it often should be. Many teams combine API testing with web application penetration testing for end-to-end coverage, or with a source code audit to find root causes faster.
Get started
Share a little about your API — size, documentation and user roles — and we'll suggest a sensible scope.
Or write to aponlineventures@gmail.com
We'll review your enquiry and reply by your preferred contact method, usually with a few scoping questions. If it's urgent, email aponlineventures@gmail.com.