Telegram · API Governance Rules
Telegram API Rules
Spectral linting rules defining API design standards and conventions for Telegram.
13 Rules
error 5
warn 6
info 2
Rule Categories
telegram
Rules
warn
telegram-operation-summary-title-case
All operation summaries must use Title Case
$.paths[*][*].summary
warn
telegram-operation-must-have-tag
All operations must have at least one tag
$.paths[*][*]
info
telegram-operation-must-have-description
All operations should have a description
$.paths[*][*]
error
telegram-operation-must-have-operationid
All operations must have an operationId
$.paths[*][*]
warn
telegram-operationid-camelcase
Operation IDs must use camelCase (Telegram method naming convention)
$.paths[*][*].operationId
error
telegram-response-200-required
All operations must define a 200 response
$.paths[*][*].responses
warn
telegram-response-must-have-schema
All 200 responses must have a content schema
$.paths[*][*].responses.200
info
telegram-schema-must-have-description
All schema properties should have descriptions
$.components.schemas[*].properties[*]
error
telegram-request-body-must-have-schema
All request bodies must have a schema
$.paths[*][*].requestBody.content[*]
warn
telegram-no-empty-descriptions
Descriptions must not be empty strings
$..description
error
telegram-info-title-required
API info must have a title
$.info
error
telegram-info-version-required
API info must have a version
$.info
warn
telegram-servers-required
API must define at least one server
$