Gutendex · API Governance Rules
Gutendex API Rules
Spectral linting rules defining API design standards and conventions for Gutendex.
13 Rules
error 8
warn 4
info 1
Rule Categories
info
no
operation
path
response
schema
servers
Rules
error
info-title-required
Info title must be present
$.info
error
info-description-required
Info description must be present
$.info
warn
info-license-required
Info license must be present (Gutendex is MIT licensed)
$.info
error
operation-operationid-required
Every operation must have an operationId
$.paths[*][get,post,put,patch,delete]
error
operation-summary-required
Every operation must have a summary
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-title-case
Operation summaries should be Title Case
$.paths[*][get,post,put,patch,delete].summary
error
operation-tags-required
Every operation must have tags
$.paths[*][get,post,put,patch,delete]
warn
operation-description-required
Every operation must have a description
$.paths[*][get,post,put,patch,delete]
error
response-description-required
Every response must have a description
$.paths[*][get,post,put,patch,delete].responses[*]
error
no-empty-descriptions
Descriptions must not be empty
$..description
error
servers-required
At least one server must be declared
$
warn
path-kebab-case
Path segments should be lowercase (Gutendex uses /books and /books/{id})
$.paths.*~
info
schema-component-references
Prefer $ref to component schemas for Book, Person, Format, BookList, Error
$.paths[*][get,post,put,patch,delete].responses[*].content[*].schema