Adamant Solutions

OpenAPI security check

Paste your OpenAPI file (JSON) to see design signals grouped by the OWASP API Security Top 10: authentication, authorization, data exposure, resource limits and inventory. Everything runs in your browser and nothing is uploaded. We only count anonymous visits (no cookies, no IP).

Do not paste a private contract you are not allowed to share. The check runs only in your browser, but remove internal host names and any example values that contain real data or secrets first. Nothing here tests your live API.

This reads the contract, not the running API, so it finds design signals and not vulnerabilities. The big ones (broken object-level authorization, for example) can only be found by testing the real API with permission. A clean result does not mean the API is secure. YAML files: convert to JSON first.

How to use this tool

  1. Paste your OpenAPI JSON.
  2. Press Check. Findings are grouped by OWASP API Security Top 10 category.
  3. Treat each finding as a question to answer about your API, then test the real API with permission.

Example

An API key declared in: query is reported under API2 because keys in URLs end up in logs. A request body that accepts isAdmin is reported under API3 as possible mass assignment.

Limits

It finds design signals in the contract, not vulnerabilities. Broken object-level authorization, the most common API flaw, can only be found by testing the running API.

Privacy and security of what you enter

The contract is processed in your browser and never uploaded. Do not paste a contract you are not allowed to share. See the privacy notice.

Want it tested properly?

We review API authentication, authorization and rate limits against the OWASP API Top 10, with your written authorization. See the security review or the free agent-readiness check.

Message us on LinkedIn