Telefono · API Governance Rules
Telefono API Rules
Spectral linting rules defining API design standards and conventions for Telefono.
11 Rules
error 5
warn 4
info 2
Rule Categories
telefono
Rules
warn
telefono-operation-summary-title-case
All operation summaries must use Title Case
$.paths[*][*].summary
error
telefono-operation-must-have-operationid
All operations must have an operationId
$.paths[*][*]
warn
telefono-operationid-camelcase
Operation IDs must use camelCase
$.paths[*][*].operationId
info
telefono-operation-must-have-description
All operations should have a description
$.paths[*][*]
warn
telefono-operation-must-have-tag
All operations must have at least one tag
$.paths[*][*]
error
telefono-number-parameter-required
Validation and lookup endpoints must require the 'number' parameter
$.paths['/validate'].get.parameters[?(@.name == 'number')]
error
telefono-response-200-required
GET operations must define a 200 response
$.paths[*].get.responses
warn
telefono-400-error-response
All operations should define a 400 Bad Request response
$.paths[*][*].responses
info
telefono-schema-properties-have-description
All schema properties should have descriptions
$.components.schemas[*].properties[*]
error
telefono-api-key-security
API must define ApiKeyAuth security scheme
$.components.securitySchemes
error
telefono-servers-required
API must define servers
$