Tray.ai · API Governance Rules
Tray.ai API Rules
Spectral linting rules defining API design standards and conventions for Tray.ai.
8 Rules
error 2
warn 6
Rule Categories
tray
Rules
warn
tray-ai-operation-summary-prefix
All operation summaries should be prefixed with "Tray.ai" to clearly identify the provider in multi-API environments.
$.paths[*][*].summary
warn
tray-ai-operation-id-camel-case
Operation IDs should use camelCase naming convention as used throughout the Tray.ai API (e.g., listConnectors, callConnector, createAuthentication).
$.paths[*][*].operationId
error
tray-ai-bearer-auth-required
All Tray.ai API endpoints require Bearer token authentication. Operations must either inherit global security or declare their own bearerAuth security.
$.paths[*][*]
warn
tray-ai-response-200-defined
All operations should define a 200 or 204 success response to document the expected output format for Tray.ai API consumers.
$.paths[*][get,post,put,patch,delete].responses
warn
tray-ai-401-response-defined
All Tray.ai operations require authentication. Each operation should document the 401 Unauthorized response for token errors.
$.paths[*][get,post,put,patch,delete].responses
warn
tray-ai-description-required
All operations should include a description field that explains the operation's purpose, token requirements, and any billing implications.
$.paths[*][*]
warn
tray-ai-tags-required
All operations should be tagged to support navigation in developer documentation and API catalog tools.
$.paths[*][*].tags
error
tray-ai-no-empty-paths
API paths should not be empty. Each path should contain at least one HTTP method.
$.paths[*]