Trigger.dev · API Governance Rules
Trigger.dev API Rules
Spectral linting rules defining API design standards and conventions for Trigger.dev.
11 Rules
error 4
warn 5
Rule Categories
trigger
Rules
error
trigger-dev-operation-id-required
All operations must have a camelCase operationId
$.paths[*][get,post,put,delete,patch]
warn
trigger-dev-operation-id-camel-case
Operation IDs must use camelCase
$.paths[*][get,post,put,delete,patch].operationId
warn
trigger-dev-operation-tags-required
All operations must have at least one tag
$.paths[*][get,post,put,delete,patch]
hint
trigger-dev-run-id-format
Run ID parameters should document the run_ prefix format
$.paths[*][*].parameters[?(@.name == 'runId')]
error
trigger-dev-path-params-required
Path parameters must be marked as required
$.paths[*][*].parameters[?(@.in == 'path')]
warn
trigger-dev-post-request-body
POST operations that create resources should have a request body
$.paths[*].post
error
trigger-dev-response-200-required
All operations must define a 200 response
$.paths[*][get,post,put,delete,patch].responses
warn
trigger-dev-response-401-required
Operations should document 401 unauthorized response
$.paths[*][get,post,put,delete,patch].responses
warn
trigger-dev-versioned-path
All API paths must be versioned
$.paths[*]~
error
trigger-dev-bearer-auth
Security scheme must use bearer authentication
$.components.securitySchemes[*]
hint
trigger-dev-run-status-enum
RunStatus must reference the canonical enum
$.components.schemas.Run.properties.status