Vertiv · API Governance Rules
Vertiv API Rules
Spectral linting rules defining API design standards and conventions for Vertiv.
10 Rules
error 1
warn 6
info 3
Rule Categories
vertiv
Rules
warn
vertiv-operation-ids-kebab-case
Operation IDs must use camelCase as per Vertiv API conventions
$.paths[*][get,post,put,patch,delete].operationId
warn
vertiv-paths-kebab-case
Path segments must use kebab-case
$.paths[*]~
warn
vertiv-require-auth-token-header
All operations (except /auth POST) must declare X-Auth-Token security
$.paths[?(@property != '/auth')][get,put,patch,delete].security
error
vertiv-response-200-must-have-schema
All 200 responses must include a schema definition
$.paths[*][get,post,put,patch,delete].responses['200'].content[*]
warn
vertiv-require-operation-tags
All operations must have at least one tag for grouping
$.paths[*][get,post,put,patch,delete]
warn
vertiv-require-operation-description
All operations must have a description
$.paths[*][get,post,put,patch,delete]
info
vertiv-error-response-schema
All non-2xx responses should reference the shared Error schema
$.paths[*][get,post,put,patch,delete].responses[4*,5*].content['application/json']
info
vertiv-status-enum-values
Status fields must use Vertiv's standard status enum values
$.components.schemas[*].properties.status.enum
info
vertiv-require-contact
API info must include contact information
$.info
warn
vertiv-server-variable-description
Server variables must have a description
$.servers[*].variables[*]