Home
Aqua Security
Aqua Security API Rules
Aqua Security API Rules
Spectral linting rules defining API design standards and conventions for Aqua Security.
36 Rules
error 12
warn 21
info 3
Rule Categories
delete
error
get
info
no
openapi
operation
operationid
parameter
paths
query
request
response
schema
security
servers
tags
Rules
error
info-title-required
Info object must have a title starting with "Aqua Security"
$.info
warn
info-description-required
Info object must have a description with at least 50 characters
$.info
error
info-version-required
Info object must have a version
$.info
warn
info-contact-required
API should have contact information
$.info
error
openapi-version-3
Use OpenAPI 3.0.x
$
error
servers-defined
Servers must be defined
$
warn
servers-https-only
Server URLs should use HTTPS
$.servers[*]
warn
paths-kebab-case
Path segments should use kebab-case
$.paths
warn
paths-no-trailing-slash
Paths should not have trailing slashes
$.paths
error
operation-summary-required
Every operation must have a summary
$.paths[*][get,post,put,delete,patch]
warn
operation-summary-prefix
Operation summaries should start with "Aqua Security"
$.paths[*][get,post,put,delete,patch]
warn
operation-description-required
Every operation should have a description
$.paths[*][get,post,put,delete,patch]
error
operation-id-required
Every operation must have an operationId
$.paths[*][get,post,put,delete,patch]
warn
operation-id-camel-case
OperationId should use camelCase
$.paths[*][get,post,put,delete,patch]
error
operation-tags-required
Every operation must have at least one tag
$.paths[*][get,post,put,delete,patch]
warn
parameter-description-required
All parameters must have a description
$.paths[*][*].parameters[*]
info
parameter-snake-case
Parameter names should use snake_case or kebab-case
$.paths[*][*].parameters[*]
warn
request-body-content-type
Request bodies should use application/json
$.paths[*][post,put,patch].requestBody.content
error
response-success-required
Every operation must have a success (2xx) response
$.paths[*][get,post,put,delete,patch].responses
warn
response-401-required
Secured endpoints should document 401 responses
$.paths[*][get,post,put,delete,patch].responses
error
response-description-required
All responses must have a description
$.paths[*][*].responses[*]
warn
schema-type-defined
Schema properties should have a type defined
$.components.schemas[*].properties[*]
info
schema-description-recommended
Top-level schemas should have a description
$.components.schemas[*]
error
security-schemes-defined
Security schemes must be defined in components
$.components
warn
security-bearer-description
Bearer auth security scheme should have a description
$.components.securitySchemes[*]
error
get-no-request-body
GET operations should not have a request body
$.paths[*].get
warn
delete-no-request-body
DELETE operations should not have a request body
$.paths[*].delete
info
delete-returns-204
DELETE operations should return 204
$.paths[*].delete.responses
error
no-empty-descriptions
Descriptions should not be empty strings
$..description
warn
tags-global-defined
Tags should be defined globally with descriptions
$
warn
servers-expected-domain
Server URLs should be on the aquasec.com domain.
$.servers[*].url
warn
query-params-casing
Query parameters should be snake_case (the dominant convention in this API).
$.paths[*][get,post,put,patch,delete].parameters[?(@.in=='query')]
warn
operationid-casing
Operation IDs should be camelCase (the dominant convention in this API).
$.paths[*][get,post,put,patch,delete].operationId
warn
schema-names-casing
Component schema names should be PascalCase (the dominant convention in this API).
$.components.schemas
warn
schema-properties-casing
Schema properties should be snake_case (the dominant convention in this API).
$.components.schemas[*].properties
warn
error-schema-defined
A shared error schema (ErrorResponse) should be defined for error payloads.
$.components.schemas
Spectral Ruleset
# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
# aqua-security — Spectral ruleset (strengthened)
# Plain Spectral. Existing hand-authored rules preserved; measured rules added
# from this provider's own OpenAPI conventions by strengthen_ruleset.py,
# then self-validated against the spec.
#
# Provenance:
# - servers-https-only: 100% of servers already https (error)
# - servers-expected-domain: 1/1 servers on aquasec.com
# - path-params-casing: snake @ 100% (n=6)
# - query-params-casing: snake @ 100% (n=8)
# - operationid-casing: camel @ 90% (n=10)
# - schema-names-casing: pascal @ 100% (n=17)
# - schema-properties-casing: snake @ 100% (n=52)
# - security: global (root) — NOT emitting operation-security-required
# - error-schema-defined: ErrorResponse
# - operation-documents-401: 100% adherence
# - pagination params observed: ['page']
# - merge: kept 30 existing, added 6 measured, upgraded 0
# - added: servers-expected-domain, query-params-casing, operationid-casing, schema-names-casing, schema-properties-casing, error-schema-defined
extends:
- spectral:oas
rules:
info-title-required:
description: Info object must have a title starting with "Aqua Security"
severity: error
given: $.info
then:
field: title
function: pattern
functionOptions:
match: ^Aqua Security
info-description-required:
description: Info object must have a description with at least 50 characters
severity: warn
given: $.info
then:
field: description
function: truthy
info-version-required:
description: Info object must have a version
severity: error
given: $.info
then:
field: version
function: truthy
info-contact-required:
description: API should have contact information
severity: warn
given: $.info
then:
field: contact
function: truthy
openapi-version-3:
description: Use OpenAPI 3.0.x
severity: error
given: $
then:
field: openapi
function: pattern
functionOptions:
match: ^3\.0\.
servers-defined:
description: Servers must be defined
severity: error
given: $
then:
field: servers
function: truthy
servers-https-only:
description: Server URLs should use HTTPS
severity: warn
given: $.servers[*]
then:
field: url
function: pattern
functionOptions:
match: ^https://
paths-kebab-case:
description: Path segments should use kebab-case
severity: warn
given: $.paths
then:
field: '@key'
function: pattern
functionOptions:
match: ^(\/[a-z0-9][a-z0-9-]*[a-z0-9]?|\{[a-z][a-zA-Z0-9_]*\})*\/?$
paths-no-trailing-slash:
description: Paths should not have trailing slashes
severity: warn
given: $.paths
then:
field: '@key'
function: pattern
functionOptions:
notMatch: \/$
operation-summary-required:
description: Every operation must have a summary
severity: error
given: $.paths[*][get,post,put,delete,patch]
then:
field: summary
function: truthy
operation-summary-prefix:
description: Operation summaries should start with "Aqua Security"
severity: warn
given: $.paths[*][get,post,put,delete,patch]
then:
field: summary
function: pattern
functionOptions:
match: ^Aqua Security
operation-description-required:
description: Every operation should have a description
severity: warn
given: $.paths[*][get,post,put,delete,patch]
then:
field: description
function: truthy
operation-id-required:
description: Every operation must have an operationId
severity: error
given: $.paths[*][get,post,put,delete,patch]
then:
field: operationId
function: truthy
operation-id-camel-case:
description: OperationId should use camelCase
severity: warn
given: $.paths[*][get,post,put,delete,patch]
then:
field: operationId
function: pattern
functionOptions:
match: ^[a-z][a-zA-Z0-9]*$
operation-tags-required:
description: Every operation must have at least one tag
severity: error
given: $.paths[*][get,post,put,delete,patch]
then:
field: tags
function: truthy
parameter-description-required:
description: All parameters must have a description
severity: warn
given: $.paths[*][*].parameters[*]
then:
field: description
function: truthy
parameter-snake-case:
description: Parameter names should use snake_case or kebab-case
severity: info
given: $.paths[*][*].parameters[*]
then:
field: name
function: pattern
functionOptions:
match: ^[a-z][a-z0-9_-]*$
request-body-content-type:
description: Request bodies should use application/json
severity: warn
given: $.paths[*][post,put,patch].requestBody.content
then:
field: '@key'
function: enumeration
functionOptions:
values:
- application/json
- multipart/form-data
- application/x-www-form-urlencoded
response-success-required:
description: Every operation must have a success (2xx) response
severity: error
given: $.paths[*][get,post,put,delete,patch].responses
then:
function: schema
functionOptions:
schema:
type: object
minProperties: 1
response-401-required:
description: Secured endpoints should document 401 responses
severity: warn
given: $.paths[*][get,post,put,delete,patch].responses
then:
field: '401'
function: truthy
response-description-required:
description: All responses must have a description
severity: error
given: $.paths[*][*].responses[*]
then:
field: description
function: truthy
schema-type-defined:
description: Schema properties should have a type defined
severity: warn
given: $.components.schemas[*].properties[*]
then:
function: schema
functionOptions:
schema:
type: object
anyOf:
- required:
- type
- required:
- $ref
schema-description-recommended:
description: Top-level schemas should have a description
severity: info
given: $.components.schemas[*]
then:
field: description
function: truthy
security-schemes-defined:
description: Security schemes must be defined in components
severity: error
given: $.components
then:
field: securitySchemes
function: truthy
security-bearer-description:
description: Bearer auth security scheme should have a description
severity: warn
given: $.components.securitySchemes[*]
then:
field: description
function: truthy
get-no-request-body:
description: GET operations should not have a request body
severity: error
given: $.paths[*].get
then:
field: requestBody
function: falsy
delete-no-request-body:
description: DELETE operations should not have a request body
severity: warn
given: $.paths[*].delete
then:
field: requestBody
function: falsy
delete-returns-204:
description: DELETE operations should return 204
severity: info
given: $.paths[*].delete.responses
then:
field: '204'
function: truthy
no-empty-descriptions:
description: Descriptions should not be empty strings
severity: error
given: $..description
then:
function: pattern
functionOptions:
match: .+
tags-global-defined:
description: Tags should be defined globally with descriptions
severity: warn
given: $
then:
field: tags
function: truthy
servers-expected-domain:
description: Server URLs should be on the aquasec.com domain.
severity: warn
given: $.servers[*].url
then:
function: pattern
functionOptions:
match: aquasec\.com
query-params-casing:
description: Query parameters should be snake_case (the dominant convention in this API).
severity: warn
given: $.paths[*][get,post,put,patch,delete].parameters[?(@.in=='query')]
then:
field: name
function: casing
functionOptions:
type: snake
operationid-casing:
description: Operation IDs should be camelCase (the dominant convention in this API).
severity: warn
given: $.paths[*][get,post,put,patch,delete].operationId
then:
function: casing
functionOptions:
type: camel
schema-names-casing:
description: Component schema names should be PascalCase (the dominant convention in this API).
severity: warn
given: $.components.schemas
then:
field: '@key'
function: casing
functionOptions:
type: pascal
schema-properties-casing:
description: Schema properties should be snake_case (the dominant convention in this API).
severity: warn
given: $.components.schemas[*].properties
then:
field: '@key'
function: casing
functionOptions:
type: snake
error-schema-defined:
description: A shared error schema (ErrorResponse) should be defined for error payloads.
severity: warn
given: $.components.schemas
then:
field: ErrorResponse
function: truthy
Every ruleset here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for spectral rules
4 MCP tools reach this
find_rulesBrowse and filter every ruleset in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/aqua-security-spectral-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms .
A second provider on the same verified email joins the account you already have.