Telefonie · API Governance Rules
Telefonie API Rules
Spectral linting rules defining API design standards and conventions for Telefonie.
12 Rules
error 4
warn 4
info 4
Rule Categories
telefonie
Rules
warn
telefonie-operation-summary-title-case
All operation summaries must use Title Case
$.paths[*][*].summary
error
telefonie-operation-must-have-operationid
All operations must have an operationId
$.paths[*][*]
warn
telefonie-operationid-camelcase
Operation IDs must use camelCase
$.paths[*][*].operationId
info
telefonie-operation-must-have-description
All operations should have a description
$.paths[*][*]
warn
telefonie-operation-must-have-tag
All operations must have at least one tag
$.paths[*][*]
info
telefonie-phone-number-e164
Phone number parameters should reference E.164 format in their descriptions
$.paths[*][*].parameters[?(@.name == 'to' || @.name == 'from' || @.name == 'phone_number')]
error
telefonie-response-200-required
GET and POST operations must define a 200 or 201 response
$.paths[*].get.responses
warn
telefonie-delete-204-response
DELETE operations should return 204
$.paths[*].delete.responses
info
telefonie-schema-properties-have-description
Schema properties should have descriptions
$.components.schemas[*].properties[*]
info
telefonie-pagination-parameters
List endpoints should support page and page_size parameters
$.paths[*].get.operationId
error
telefonie-security-required
All operations must have security defined
$.paths[*][*]
error
telefonie-servers-required
API must define servers
$