The Cat API · API Governance Rules
The Cat API API Rules
Spectral linting rules defining API design standards and conventions for The Cat API.
10 Rules
error 3
warn 7
Rule Categories
catapi
Rules
warn
catapi-operations-must-have-tags
All Cat API operations must be tagged (Images, Breeds, Favourites, Votes, Categories).
$.paths[*][*]
warn
catapi-operations-must-have-summary
All operations must have a summary in Title Case.
$.paths[*][*]
error
catapi-operations-must-have-operationid
All operations must define an operationId for SDK generation.
$.paths[*][*]
error
catapi-responses-must-include-200
All read operations must define a 200 success response.
$.paths[*][get].responses
warn
catapi-responses-must-include-401
All write operations should document a 401 Unauthorized response.
$.paths[*][post].responses
warn
catapi-parameters-must-have-descriptions
All path and query parameters must have descriptions.
$.paths[*][*].parameters[*]
warn
catapi-collection-paths-use-plural-nouns
Collection paths must use plural nouns (e.g., /images, /breeds, /votes, /favourites).
$.paths
warn
catapi-path-parameters-use-snake-case
Path parameter names must use snake_case.
$.paths[*][*].parameters[?(@.in == 'path')]
warn
catapi-responses-define-content-type
All 200 responses should define a content type.
$.paths[*][get].responses.200
error
catapi-info-must-have-version
The API info object must include a version.
$.info