VD HOSTS
Discuss your project

API security testing

APIs carry your data. Test them like they matter.

REST and GraphQL APIs tested for broken authorisation, data exposure and abuse, against the OWASP API Security Top 10.

Why teams call us

Problems this solves

  • 01

    One ID change exposes another customer

    Broken object-level authorisation lets a user read or change records by changing an identifier.

  • 02

    APIs return more than the app shows

    Mobile and web apps often hide fields that the API still sends to anyone who asks.

  • 03

    Partners and integrations multiply access

    Third-party keys and webhooks widen who can call what.

  • 04

    No limits on expensive operations

    Missing rate limits allow scraping, brute force and cost-driven abuse.

Our approach

Modern applications are mostly APIs, and attackers call them directly. We test each endpoint for who can call it, what it returns and how it behaves under abuse, using the OWASP API Security Top 10 (2023) as the baseline.

Testing covers authentication and token handling, object- and function-level authorisation, mass assignment, input validation, rate limiting, and the security of webhooks and partner integrations.

Cybersecurity

What is included

  • Authorisation testing

    Object-level and function-level authorisation checked across users and roles.

  • Token and key handling

    JWTs, OAuth flows, API keys and their expiry and scope.

  • Data exposure

    Responses reviewed for fields and records that should not be returned.

  • Rate limiting and abuse

    Brute force, enumeration and resource-consumption checks.

  • Webhooks and integrations

    Signature verification, replay protection and partner access.

  • GraphQL specifics

    Introspection, query depth and batching abuse.

What you receive

  • Endpoint inventory and coverage matrix
  • Findings with request and response evidence
  • Risk rating and impact per finding
  • Fix guidance per framework
  • Retest and closure report

Technology we work with

  • OWASP API Security Top 10
  • OpenAPI
  • GraphQL
  • OAuth 2.0
  • JWT
  • Postman
  • Burp Suite

Industries

How an engagement runs

Every engagement starts with a signed agreement and an advance payment as set out in your proposal. Work begins once both are complete.

  1. 01

    Scope

    API documentation, environments, test credentials per role and exclusions agreed.

  2. 02

    Map

    Endpoints, parameters and data flows documented.

  3. 03

    Test

    Authorisation, authentication, input and abuse testing.

  4. 04

    Report and retest

    Findings delivered with evidence; fixes retested.

Ready to start? Talk to us directly.

Tell us what you need in a few lines. A specialist replies with next steps and a written proposal before any work begins.

Frequently asked questions

Can't find your answer? Ask us

Do you need API documentation?
It helps a lot. An OpenAPI specification or a Postman collection lets us cover every endpoint. Without it we map the API from the client application.
Can you test partner or open-banking APIs?
Yes, within the scope your agreements allow. We confirm authorisation for any third-party system before testing.
Do you test GraphQL?
Yes, including introspection, deeply nested queries and batching attacks.

Start with a conversation.

Share a few details. A specialist replies with next steps, usually starting with a short call.

VD Hosts