target · API Governance Rules
target API Rules
Spectral linting rules defining API design standards and conventions for target.
12 Rules
error 3
warn 8
info 1
Rule Categories
target
Rules
warn
target-operation-ids-camel-case
Operation IDs must use camelCase
$.paths[*][*].operationId
warn
target-tags-title-case
Tags must use Title Case
$.tags[*].name
warn
target-path-kebab-case
Path segments must use kebab-case
$.paths[*]~
warn
target-paths-versioned
All paths must include a version prefix (e.g., /v1/, /v3/)
$.paths[*]~
error
target-operation-summary-exists
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
warn
target-operation-description-exists
All operations must have a description
$.paths[*][get,post,put,patch,delete]
error
target-responses-200-exists
All operations must have a 200 response
$.paths[*][get,post,put,patch,delete].responses
warn
target-responses-401-exists
Secured operations must document 401 response
$.paths[*][get,post,put,patch,delete].responses
warn
target-parameters-description
All parameters must have descriptions
$.paths[*][*].parameters[*]
error
target-bearer-auth-defined
bearerAuth security scheme must be defined
$.components.securitySchemes
warn
target-info-contact
API must include contact information
$.info
info
target-schema-properties-described
Schema properties should have descriptions
$.components.schemas[*].properties[*]