Tremendous · API Governance Rules
Tremendous API Rules
Spectral linting rules defining API design standards and conventions for Tremendous.
12 Rules
error 2
warn 6
info 4
Rule Categories
tremendous
Rules
warn
tremendous-operation-id-camel-case
Operation IDs must use camelCase
$.paths[*][*].operationId
warn
tremendous-summary-title-case
Operation summaries must use Title Case
$.paths[*][*].summary
error
tremendous-security-defined
All operations must define security requirements
$.paths[*][get,post,put,patch,delete]
error
tremendous-response-200-get
All GET operations must define a 200 response
$.paths[*].get
warn
tremendous-response-401-defined
Authenticated operations should define a 401 response
$.paths[*][get,post,put,patch,delete]
warn
tremendous-tag-defined
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
info
tremendous-bearer-auth
Tremendous API uses Bearer token (API key) authentication
$.components.securitySchemes.BearerAuth
warn
tremendous-path-snake-case
Path parameters use snake_case
$.paths[*]~
warn
tremendous-post-request-body
POST operations should define a request body
$.paths[*].post
info
tremendous-rate-limit-response
Tremendous API enforces rate limits - 429 should be documented
$.paths[*][get,post]
info
tremendous-idempotency-external-id
Create operations should document external_id for idempotency
$.paths['/orders'].post.requestBody.content.application/json.schema
info
tremendous-list-pagination
List operations should support pagination with offset and limit
$.paths[*].get