API Security
Probe (API security) tests REST and GraphQL APIs. It fuzzes your API from its OpenAPI or GraphQL schema, runs OWASP API Top 10 checks and BOLA probes, and looks for endpoints your schema does not document. Scans can authenticate with your token or API key.
What API Security tests
Horizontal access control failures: reaching another user's resources by changing an identifier.
Functions that should be restricted to a role but answer any authenticated caller.
JWT weaknesses and authentication flaws on API endpoints.
Endpoints that accept fields a client should not be able to set.
Verbose error messages, permissive CORS and debug endpoints left open.
Valid and invalid requests generated from your schema to surface injection flaws and unhandled errors.
GraphQL-specific weaknesses such as exposed introspection.
Missing rate limits on authentication and sensitive endpoints.
Discovery of endpoints that exist on the API host but are missing from the schema.
Schema, scan, report
- 1
Point at your API
Enter the API base URL on a target you have verified and, optionally, an OpenAPI or GraphQL schema URL. Without one, common schema paths such as /openapi.json are probed.
- 2
Configure authentication
Supply a bearer token, basic auth credentials, or an API key in a header or query parameter. The BOLA, template and discovery probes use bearer tokens.
- 3
Fuzzing and checks
Spoorder fuzzes the endpoints, runs the OWASP API Top 10 checks and BOLA probes, and looks for undocumented endpoints.
- 4
Findings with evidence
Each finding carries its evidence, CWE mapping and remediation guidance.
GET /api/v1/users/12345/documents HTTP/1.1
Authorization: Bearer <user_456_token>
---
HTTP/1.1 200 OK
{
"documents": [
{"id": "doc-001", "owner": "user_12345", ...}
]
}Spoorder API Security vs a general web scanner
| Criterion | Spoorder | a general web scanner |
|---|---|---|
| Schema support | OpenAPI and GraphQL schemas, or auto-detect | Crawl-based discovery only |
| Authenticated scanning | Bearer token, basic, API key in header or query | Often manual setup |
| BOLA testing | Built-in BOLA and BFLA probes | Not included |
| GraphQL support | Dedicated GraphQL checks | REST only |
| Endpoint discovery | Finds undocumented endpoints | Documented endpoints only |
What API schema formats does Spoorder support?
OpenAPI and Swagger schemas for REST APIs and GraphQL schemas, supplied by URL. If you leave the schema empty, Spoorder probes common schema paths on the API host, and fuzzes without a schema if it finds none.
How does Spoorder test authenticated APIs?
Provide a bearer token, basic auth credentials, or an API key in a header or query parameter when you configure the scan. Fuzzing uses whichever method you choose. The BOLA, template and discovery probes support bearer tokens and run unauthenticated otherwise.
Can API security testing run in CI/CD?
Yes. A pipeline step can start an API scan and evaluate a security gate with an API key that has the scan scope. The target must be verified first. The CI/CD docs have the requests.
Does API scanning work with internal or private APIs?
Scans run from Spoorder's infrastructure, so the API must be reachable from the internet and belong to a target you have verified you own. Private and internal addresses are blocked.
What is the difference between DAST and API Security scanning?
DAST crawls a web application to find its pages and forms. API Security scanning works from your API schema, so it reaches endpoints that have no UI, and it tests API-specific flaws such as BOLA and mass assignment.
What plan and credits does it need?
API Security is included from the Builder plan ($69/mo). A scan costs 12 credits.
Start scanning
Start with a free health check. API Security is included from Builder ($69/mo).