Hunter · API Governance Rules
Hunter API Rules
Spectral linting rules defining API design standards and conventions for Hunter.
10 Rules
error 5
warn 4
info 1
Rule Categories
hunter
Rules
error
hunter-operation-summary-required
All operations must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
hunter-operation-summary-title-case
Operation summaries must use Title Case starting with 'Hunter'.
$.paths[*][get,post,put,patch,delete].summary
error
hunter-operation-description-required
All operations must have a description.
$.paths[*][get,post,put,patch,delete]
error
hunter-operation-id-camelcase
operationId must be camelCase.
$.paths[*][get,post,put,patch,delete].operationId
error
hunter-tags-required
Every operation must have at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
hunter-security-defined
Authenticated endpoints must declare a security scheme.
$.paths[*][get,post,put,patch,delete]
error
hunter-server-https
Servers must use HTTPS.
$.servers[*].url
warn
hunter-base-path-v2
All Hunter servers should target the v2 base path.
$.servers[*].url
warn
hunter-error-schema-defined
An Error schema must be defined.
$.components.schemas
info
hunter-snake-case-params
Hunter query parameters use snake_case.
$.paths[*][*].parameters[?(@.in == 'query')].name