Spot by NetApp · API Governance Rules
Spot by NetApp API Rules
Spectral linting rules defining API design standards and conventions for Spot by NetApp.
11 Rules
error 6
warn 5
Rule Categories
spot
Rules
error
spot-bearer-auth
Spot API must use Bearer token authentication.
$.components.securitySchemes
warn
spot-response-envelope
Spot API responses should use the request/response envelope pattern.
$.paths[*].get.responses.200.content.application/json.schema
warn
spot-cloud-path-prefix
Cloud provider paths should be prefixed with the provider name.
$.paths
error
spot-operation-id
All operations must have an operationId.
$.paths[*][*]
error
spot-operation-id-camel-case
OperationIds must use camelCase.
$.paths[*][*].operationId
error
spot-operation-tags
All operations must have at least one tag.
$.paths[*][*]
warn
spot-summary-title-case
Operation summaries must use Title Case.
$.paths[*][*].summary
warn
spot-account-id-param
Operations that are account-scoped should accept an accountId query parameter.
$.paths[*].get
error
spot-200-response
All operations must define a 200 response.
$.paths[*][*]
warn
spot-401-response
Operations should document the 401 unauthorized response.
$.paths[*][*]
error
spot-server-production
API must define the Spot production server URL.
$.servers[*].url