Toro · API Governance Rules
Toro API Rules
Spectral linting rules defining API design standards and conventions for Toro.
10 Rules
error 3
warn 7
Rule Categories
toro
Rules
warn
toro-operation-id-camel-case
Operation IDs must use camelCase
$.paths[*][*].operationId
warn
toro-operation-summary-title-case
Operation summaries must use Title Case
$.paths[*][*].summary
warn
toro-paths-kebab-case
API paths must use kebab-case for path segments
$.paths[*]~
error
toro-must-have-tags
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
error
toro-responses-must-have-description
All responses must have a description
$.paths[*][*].responses[*]
error
toro-must-have-200-or-201
All operations must define a success response (200 or 201)
$.paths[*][get,post,put,patch,delete].responses
warn
toro-parameters-must-have-description
All parameters must have descriptions
$.paths[*][*].parameters[*]
warn
toro-request-body-content-type
Request bodies should use application/json content type
$.paths[*][post,put,patch].requestBody.content
warn
toro-error-response-schema
Error responses (4xx, 5xx) should reference a schema
$.paths[*][*].responses[4xx,5xx]
warn
toro-list-operations-must-support-pagination
List operations should support pagination parameters
$.paths[*][get][?(@.operationId =~ /^list/)]