Sophos · API Governance Rules
Sophos API Rules
Spectral linting rules defining API design standards and conventions for Sophos.
10 Rules
error 3
warn 6
info 1
Rule Categories
sophos
Rules
error
sophos-requires-api-key-header
All Sophos SIEM operations must require the x-api-key header parameter
$.paths[*][get,post,put,patch,delete].parameters[?(@.name == 'x-api-key')]
warn
sophos-operation-summary-title-case
Operation summaries must use Title Case
$.paths[*][get,post,put,patch,delete].summary
warn
sophos-operation-has-tags
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
info
sophos-cursor-pagination
Sophos APIs use cursor-based pagination; use 'cursor' query parameter
$.paths[*][get].parameters[?(@.name == 'limit')]
warn
sophos-401-response
Operations with auth must document 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
error
sophos-operation-id-required
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
sophos-operation-id-camel-case
OperationId must use camelCase convention
$.paths[*][get,post,put,patch,delete].operationId
warn
sophos-response-schema-defined
Successful responses must have a schema
$.paths[*][get,post,put,patch,delete].responses['200','201'].content['application/json']
warn
sophos-tags-title-case
All tags in the spec must use Title Case
$.tags[*].name
error
sophos-security-defined
Security must be defined at the global or operation level
$