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 accreditation for VA, Pen Test and SOC, held by our testing partner
  • TÜV SÜD ISO/IEC 27001 certification
  • SAC accredited ISMS certification
  • bizSAFE Level 3
  • CREST-accredited testing partner, globally recognised standards
API penetration testing: laptop showing application code in a dark room
  • 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.

Sounds familiar? Talk to an expert

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. 1

    Map

    Every endpoint, method and role.

  2. 2

    Test

    Access control, input and limits.

  3. 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.

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)

  1. API1 Broken object level authorisation
  2. API2 Broken authentication
  3. API3 Broken object property level authorisation
  4. API4 Unrestricted resource consumption
  5. API5 Broken function level authorisation
  6. API6 Unrestricted access to sensitive business flows
  7. API7 Server side request forgery
  8. API8 Security misconfiguration
  9. API9 Improper inventory management
  10. API10 Unsafe consumption of APIs

How our API penetration testing process works

Five steps from specs to retest.

  1. 01

    Collect specs

    You:
    Share specs and test accounts.
    We:
    Send a fixed quote and plan.
    Within 24h
  2. 02

    Automated testing

    You:
    Keep the test API up.
    We:
    Map and probe every endpoint.
    1 day
  3. 03

    Manual access and logic testing

    You:
    Nothing.
    We:
    Test roles, records and rules.
    2 to 4 days
  4. 04

    Report

    You:
    Join with your developers.
    We:
    Explain findings and fixes.
    3 to 5 days
  5. 05

    Retest

    You:
    Ship the fixes.
    We:
    Retest and attest.
    When you are ready

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 quote

What 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.

Get an API pentest quote

Tell us roughly how many endpoints and roles you have.

Required

We reply within one working day. Your details stay with us.

API penetration testing FAQs

Still unsure? Ask us directly on a free call.

API penetration testing: free consultation with a Genic Solutions security advisor in Singapore

Get an API pentest quote

30 minutes, no obligation, with a security consultant.

Required

We reply within one working day. Your details stay with us.