Daytona · API Governance Rules
Daytona API Rules
Spectral linting rules defining API design standards and conventions for Daytona.
10 Rules
error 6
warn 4
Rule Categories
daytona
Rules
error
daytona-paths-kebab-case
Path segments MUST be lowercase kebab-case (matching Daytona's docker-registry, object-storage, api-keys conventions).
$.paths.*~
warn
daytona-tags-lowercase-kebab
Tag names MUST be lowercase kebab-case (matching Daytona's convention).
$.tags[*].name
error
daytona-operation-has-operationId
Every operation MUST declare an operationId for SDK code generation.
$.paths[*][get,post,put,patch,delete,head,options]
warn
daytona-operationId-camelCase
operationId MUST be camelCase verbNoun (e.g., createSandbox, listSnapshots).
$.paths[*][get,post,put,patch,delete].operationId
error
daytona-operation-has-tag
Every operation MUST be tagged so it can be grouped in the API reference (Sandbox, Snapshots, Toolbox, etc.).
$.paths[*][get,post,put,patch,delete]
error
daytona-operation-has-summary
Every operation MUST declare a summary for the Scalar API reference.
$.paths[*][get,post,put,patch,delete]
error
daytona-security-bearer-required
A bearer auth scheme MUST be declared in components.securitySchemes.
$.components.securitySchemes
error
daytona-servers-required
Specs MUST declare at least one server. Use https://app.daytona.io/api for the control plane or https://proxy.app.daytona.io/toolbox for the in-sandbox Toolbox.
$.servers
warn
daytona-contact-info
info.contact MUST be set with Daytona's support contact ([email protected]).
$.info
warn
daytona-schema-descriptions
Components schemas SHOULD have a description so SDK comments are populated.
$.components.schemas[*]