The API is the product

If the UI hides it, the API still answers to Sumrite.

Most of the serious findings we ship are not on the marketing site. They are one changed identifier in a JSON call. This guide is how we trace that path.

Where APIs fail

Five patterns we test first.

Aligned with the OWASP API risks your security questionnaire already names, described the way we test them.

API1

Object-level access

Every id in the path or body is swapped for another tenant’s id. If the JSON comes back, it is a finding.

API2

Broken authentication

Tokens that survive logout, reset links that do not expire, and API keys sitting in a mobile build.

API3

Object property access

A profile update that also accepts role or isAdmin because the server binds every field.

API4

Unrestricted use

Password guesses, OTP retries, and expensive endpoints with no limit. We measure what one account can do in a minute.

API5

Function-level access

Admin methods called with a normal user token. The UI never showed the button. The route still exists.

API8

Misconfiguration

Verbose errors, CORS that reflects any origin with credentials, and debug routes left on in production.

What you receive

A request, a response, a fix.

API findings in a Sumrite report include the exact call, the data that should not have returned, and the check your engineers should add. Retest is included before the report.

Scope an API test