Web Application, API & Mobile App Testing
API penetration testing for REST, SOAP and GraphQL: we check that each customer only ever sees their own data, that normal users cannot reach admin functions, and that your APIs hold up under automated abuse. Mapped to the OWASP API Security Top 10.
- OWASP API Security Top 10
- Authorisation tested per role
- Free retest and attestation letter




- CREST-accredited testing partner, globally recognised standards

-
REST, SOAP, GraphQL From your API specs
-
Per-user access checks Each customer sees only theirs
-
Limits tested And over-sharing of data
-
Free retest Plus an attestation letter
When do you need API penetration testing?
APIs now carry most of your data. These are the moments to test them.
Public or partner APIs are launching
Partners and customers will soon connect to your systems directly.
Your mobile app runs on APIs
The app is only as safe as the API behind it.
Open banking or integrations
Partners, regulators or banks ask for evidence that your APIs are secure.
Scans found nothing
Scanners rarely understand who should see what, so a clean scan can be misleading.
What is API penetration testing?
API penetration testing is an authorised security test of the application programming interfaces your apps, partners and customers use. Testers check authentication, access control between users and roles, input handling, rate limits and the data each endpoint returns, then report what needs fixing and how.
The most serious API issues are about business rules: whether the API checks that a record really belongs to the person asking for it. Those need a person who understands your data, which is why we test by hand as well as with tools. APIs rarely stand alone, so we often test them together with web application penetration testing or mobile app penetration testing of the front ends that use them, in one penetration testing engagement.
How it works
-
1
Map
Every endpoint, method and role.
-
2
Test
Access control, input and limits.
-
3
Fix
Developer-ready fixes, then retest.
Our API penetration testing services
Four checks that catch most serious API issues. Pick one to see what a secure API does, and what a weak one does instead.
Each customer sees only their own records
Broken object-level authorisation (BOLA) is the most common serious API issue: the API checks that someone is signed in, but not that the record belongs to them.
What we check: Every endpoint that looks up a record by ID, using accounts from different customers and tenants.
Someone asks
Customer A asks the API for order number 1043, which belongs to Customer B.
A secure API
Refuses the request, because the order is not Customer A’s.
A weak API
Returns Customer B’s order, address and total to Customer A.
Normal users cannot use admin functions
Broken function-level authorisation (BFLA) happens when admin features are hidden in the app but not protected on the server.
What we check: Admin and internal functions, tried with each lower-privileged role.
Someone asks
A normal user tries an admin-only function, such as removing another user.
A secure API
Refuses, because the user does not have the admin role.
A weak API
Carries out the action, because only the app hid the button.
Automated abuse is slowed down
Without rate limits, scripts can guess one-time codes, try leaked passwords or copy out your data far faster than any person could.
What we check: Sign-in, one-time code, search and export endpoints under automated load.
Someone asks
A script sends thousands of sign-in or code attempts in a few minutes.
A secure API
Slows down and then blocks the attempts, and alerts your team.
A weak API
Keeps answering every attempt until one of them works.
Responses only carry what each role should see
APIs often send whole database records and rely on the app to hide fields. Anyone calling the API directly sees everything.
What we check: Every response, compared with what each role is meant to see.
Someone asks
A customer views their own profile.
A secure API
Sends back only the fields the profile screen needs.
A weak API
Also sends internal fields the app never shows, such as staff notes or system flags.
Protocols we test
- REST
- SOAP
- GraphQL
We work from your OpenAPI (Swagger) files, Postman collections or GraphQL schema, plus test accounts for each role.
Mapped to the OWASP API Security Top 10 (2023)
- API1 Broken object level authorisation
- API2 Broken authentication
- API3 Broken object property level authorisation
- API4 Unrestricted resource consumption
- API5 Broken function level authorisation
- API6 Unrestricted access to sensitive business flows
- API7 Server side request forgery
- API8 Security misconfiguration
- API9 Improper inventory management
- API10 Unsafe consumption of APIs
How our API penetration testing process works
Five steps from specs to retest.
-
01
Collect specs
- You:
- Share specs and test accounts.
- We:
- Send a fixed quote and plan.
-
02
Automated testing
- You:
- Keep the test API up.
- We:
- Map and probe every endpoint.
-
03
Manual access and logic testing
- You:
- Nothing.
- We:
- Test roles, records and rules.
-
04
Report
- You:
- Join with your developers.
- We:
- Explain findings and fixes.
-
05
Retest
- You:
- Ship the fixes.
- We:
- Retest and attest.
Typical timeline: a quote within 24 hours, testing in 3 to 6 working days and your report 3 to 5 days later.
Get an API pentest quoteWhat you receive
Findings your developers can act on, endpoint by endpoint.
- Findings by endpoint Each issue tied to the endpoint, method and role.
- OWASP API mapping Every finding tagged to its API Top 10 category.
- Fix guidance Framework-specific advice for your developers.
- Walkthrough call Your developers talk to the testers.
- Retest letter Attestation for partners and auditors.
Standards and regulations we help you meet
-
OWASP API Top 10
Findings mapped to each category, so you can show which risks were tested.
-
MAS TRM
Supports independent security testing of APIs exposed to customers and partners.
-
PDPA
Shows reasonable security arrangements protect the personal data your APIs return.
We help you meet these requirements; certification itself is issued by the relevant body.
Why choose Genic Solutions for API penetration testing
A Singapore team on your time zone
Your API pentest is scoped, run and debriefed by people based here, who understand MAS TRM, PDPA and local procurement.
Ubi Techpark, Singapore
A CREST-accredited partner
Testing is delivered with a CREST-accredited partner, to the standard auditors, regulators and enterprise clients ask for by name.
CREST-accredited partner
Named testers
You know who is testing your systems before the work starts.
Named lead tester
A fixed quote within one working day
Send us the scope and get a fixed price, a test window and a report date, with no open-ended billing.
Quote within 24 hours
Free retest after you fix
Once your team has fixed the findings, we retest them and issue an attestation letter at no extra cost.
Retest included
Plain-English executive summary
Management gets a short summary of business risk; engineers get technical detail and step-by-step fixes.
Two audiences, one report
How much does API penetration testing cost?
The price depends on the number of endpoints, roles and how complex the business rules are.
- Scope size How many applications, IP addresses, APIs or cloud accounts are in scope.
- User roles and complexity Logged-in testing across several roles, payment flows or complex business logic takes longer.
- Testing depth Black box, grey box or white box, and whether source code or architecture review is included.
- Retests and timing One free retest is included. Weekend windows or urgent start dates can change the price.
Thanks, .
A security advisor will contact you within one working day to arrange your free consultation.
API penetration testing FAQs
Still unsure? Ask us directly on a free call.
-
API documentation such as OpenAPI files, a Postman collection or a GraphQL schema, a test environment, and test accounts for each role. Two accounts per role let us check that users cannot see each other’s data.
-
Yes. GraphQL needs its own checks, such as query depth and complexity limits, introspection settings and access control on each field, on top of the usual API tests.
-
A web app test works through the browser interface. An API test calls the endpoints directly, the way partners, mobile apps and attackers do, which reaches functions and data the interface never shows.
Thanks, .
We will reply with a fixed API pentest quote within one working day.