Toyota · API Governance Rules
Toyota API Rules
Spectral linting rules defining API design standards and conventions for Toyota.
9 Rules
error 3
warn 6
Rule Categories
toyota
Rules
warn
toyota-operation-id-camel-case
Operation IDs must use camelCase
$.paths[*][*].operationId
warn
toyota-operation-summary-title-case
Operation summaries must use Title Case
$.paths[*][*].summary
warn
toyota-paths-kebab-case
API paths must use kebab-case
$.paths[*]~
error
toyota-must-have-tags
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
warn
toyota-vin-path-parameter
VIN path parameters should have proper length constraints
$.paths[*][*].parameters[?(@.name == 'vin' && @.in == 'path')]
error
toyota-must-have-200-or-201
All operations must define a success response
$.paths[*][get,post,put,patch,delete].responses
warn
toyota-pagination-on-list-operations
List operations should support pagination parameters
$.paths[*][get][?(@.operationId =~ /^list/)]
error
toyota-vehicle-endpoints-auth
All vehicle endpoints must require authentication
$.paths[/vehicles*][get,post,put,patch,delete]
warn
toyota-coordinates-format
Latitude and longitude fields should use double format
$.components.schemas[*].properties[latitude,longitude]