API Penetration Testing
API penetration testing is a manual security test of your REST or GraphQL APIs. Testers use accounts for each role to check whether the API lets users read or change data they shouldn't, following the OWASP API Security Top 10.
- Manual, expert-led testing
- CVSS-rated report with fixes
- Retest after you fix
- Written scope before work starts
Talk to our Security Experts
Tell us what needs testing, then pick a 30-minute slot.
Get a tailored scope, timeline and pricing on the call.
OWASP API Top 10 issues we test
- Broken object-level authorisation (BOLA)
- Broken authentication
- Broken object property-level authorisation
- Unrestricted resource consumption
- Broken function-level authorisation
- Unrestricted access to sensitive business flows
- Server-side request forgery
- Security misconfiguration
- Improper inventory management
- Unsafe consumption of third-party APIs
What to share before testing
- OpenAPI/Swagger file or Postman collection
- Test accounts for each role and tenant
- Base URLs for the target environment
- Any rate limits we should respect
Requirements Indian businesses usually test for
In India, the trigger for a test is often regulatory. RBI expects regulated entities and their technology vendors to run periodic VAPT. SEBI's cybersecurity framework asks market intermediaries for regular testing. CERT-In directions require organisations to maintain security practices and report incidents. The Digital Personal Data Protection (DPDP) Act 2023 requires reasonable security safeguards for personal data.
Enterprise customers also ask vendors for a recent third-party pentest report during security reviews. We write reports so the same document can be shared with a regulator, an auditor or a customer's security team.
How the engagement runs
1. Scoping call (30 minutes)
We agree targets, user roles, environments, testing windows and the compliance reason for the test.
2. Written scope and quote
You get a scope document and an INR or USD quote based on the real size of the work.
3. Discovery and manual testing
Automated tooling for coverage, then manual testing of authentication, access control and business logic.
4. Report
Executive summary, CVSS-rated findings with evidence, reproduction steps and remediation guidance.
5. Retest
Once your team ships fixes, we verify each finding and issue an updated report.
What the report contains
- Executive summary for leadership, customers and auditors
- Findings rated by CVSS severity with screenshots and request evidence
- Step-by-step reproduction for your developers
- Specific remediation guidance, not generic advice
- Compliance mapping (ISO 27001, SOC 2, PCI DSS, RBI, SEBI, CERT-In guidelines) where relevant
- Retest status showing which findings are open and closed
Certifications our testers hold
Every engagement is led by a certified senior tester.
Frequently asked questions
Can you test internal or partner APIs?
Yes, with VPN or allow-listed access.
How much does it cost?
Price depends on the number of targets, user roles and depth of manual testing. Use the VAPT cost estimator for an INR range, or book a call for a written quote.