Swagger · API Governance Rules
Swagger API Rules
Spectral linting rules defining API design standards and conventions for Swagger.
10 Rules
error 4
warn 6
Rule Categories
swagger
Rules
warn
swagger-oas-operations-have-tags
All OpenAPI operations must have at least one tag for organization
$.paths[*][get,put,post,delete,patch,options,head,trace]
error
swagger-oas-operations-have-summaries
All OpenAPI operations must have a summary in Title Case
$.paths[*][get,put,post,delete,patch,options,head,trace]
warn
swagger-oas-summaries-title-case
OpenAPI operation summaries should use Title Case
$.paths[*][get,put,post,delete,patch,options,head,trace].summary
error
swagger-oas-operations-have-operation-ids
All OpenAPI operations must have an operationId for code generation
$.paths[*][get,put,post,delete,patch,options,head,trace]
warn
swagger-oas-operations-have-descriptions
All OpenAPI operations should have a description
$.paths[*][get,put,post,delete,patch,options,head,trace]
error
swagger-oas-path-params-required
All path parameters must be marked as required
$.paths[*][*].parameters[?(@.in == 'path')]
warn
swagger-oas-schemas-have-descriptions
All component schemas must have a description
$.components.schemas[*]
error
swagger-oas-info-required-fields
API info object must have title, description, and version
$.info
warn
swagger-oas-responses-have-descriptions
All response objects must have a description
$.paths[*][*].responses[*]
warn
swagger-oas-paths-kebab-case
API paths should use kebab-case (lowercase with hyphens, no underscores)
$.paths[*]~