Telesign · API Governance Rules
Telesign API Rules
Spectral linting rules defining API design standards and conventions for Telesign.
12 Rules
error 4
warn 7
Rule Categories
telesign
Rules
warn
telesign-operation-summary-title-case
All operation summaries must use Title Case
$.paths[*][*].summary
error
telesign-operation-must-have-operationid
All operations must have an operationId
$.paths[*][*]
warn
telesign-operationid-kebab-case
Operation IDs should use camelCase
$.paths[*][*].operationId
hint
telesign-phone-number-parameter
Phone number parameters should be named 'phone_number' or 'complete_phone_number' and include country code in their description
$.paths[*][*].parameters[?(@.name == 'phone_number' || @.name == 'complete_phone_number')]
warn
telesign-reference-id-response
Successful responses should include a reference_id field for transaction tracking
$.paths[*].post.responses.200.content['application/json'].schema.properties
warn
telesign-status-object-in-response
Successful responses should include a status object with code and description
$.paths[*].post.responses.200.content['application/json'].schema.properties
error
telesign-requires-basic-auth
All paths must require BasicAuth security
$.paths[*][*]
error
telesign-server-must-be-telesign
Server URL must point to rest-ww.telesign.com
$.servers[*].url
warn
telesign-response-must-have-400
POST operations must handle 400 Bad Request
$.paths[*].post.responses
error
telesign-response-must-have-401
All operations must handle 401 Unauthorized
$.paths[*][*].responses
warn
telesign-response-must-have-429
POST operations must handle 429 rate limiting
$.paths[*].post.responses
warn
telesign-account-lifecycle-enum
account_lifecycle_event must use the approved enum values
$.paths[*][*]..properties.account_lifecycle_event