Snow Software · API Governance Rules
Snow Software API Rules
Spectral linting rules defining API design standards and conventions for Snow Software.
9 Rules
warn 4
info 5
Rule Categories
snow
Rules
warn
snow-operation-id-camel-case
Operation IDs must use camelCase naming convention
$.paths[*][*].operationId
warn
snow-server-region-variable
Snow Atlas server URLs should include a {region} variable for multi-region support
$.servers[*].url
info
snow-pagination-params
Collection endpoints should support page_number and page_size parameters
$.paths[*].get.parameters[*].name
info
snow-filter-param
Snow Atlas APIs should support filter query parameters for collection endpoints
$.paths[*].get
warn
snow-operation-tag
All operations must have at least one tag
$.paths[*][get,post,put,delete,patch]
warn
snow-operation-summary
All operations must have a summary in Title Case
$.paths[*][get,post,put,delete,patch]
info
snow-operation-description
All operations should have a description
$.paths[*][get,post,put,delete,patch]
info
snow-hateoas-response
Snow Atlas collection responses follow a HATEOAS pattern with pagination links
$.paths[*][get].responses['200'].content['application/json'].schema
info
snow-400-error-defined
Operations should define a 400 Bad Request response
$.paths[*][post,put,patch].responses