Torii · API Governance Rules
Torii API Rules
Spectral linting rules defining API design standards and conventions for Torii.
10 Rules
error 4
warn 5
Rule Categories
torii
Rules
warn
torii-operation-summary-prefix
Operation summaries should start with "Torii" prefix
$.paths[*][get,post,put,patch,delete].summary
error
torii-operation-id-required
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
error
torii-operation-summary-required
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
error
torii-bearer-auth-defined
BearerAuth security scheme must be defined
$.components.securitySchemes
hint
torii-api-version-header
API version header should be consistently defined via $ref
$.paths[*][get,post,put,patch,delete].parameters[?(@.name == 'X-API-Version')]
warn
torii-pagination-parameters
Collection GET endpoints should support size and cursor pagination
$.paths[?([email protected](/\{/))]..get.parameters[?(@.name=='size')]
warn
torii-unauthorized-response
Protected endpoints should document 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
warn
torii-rate-limited-response
Endpoints should document 429 Rate Limited response
$.paths[*][get,post,put,patch,delete].responses
error
torii-request-body-required
Request bodies for write operations must be marked required
$.paths[*][post,put,patch].requestBody
warn
torii-path-param-description
Path parameters should have descriptions
$.paths[*][*].parameters[?(@.in=='path')]