Theneo · API Governance Rules
Theneo API Rules
Spectral linting rules defining API design standards and conventions for Theneo.
10 Rules
error 2
warn 8
Rule Categories
theneo
Rules
warn
theneo-operation-ids-camel-case
All operationIds must use camelCase.
$.paths[*][*].operationId
warn
theneo-operation-summary-title-case
All operation summaries must use Title Case.
$.paths[*][*].summary
warn
theneo-path-kebab-case
All path segments must use kebab-case.
$.paths[*]~
error
theneo-tags-required
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
theneo-api-key-security
All operations must declare the apiKey security scheme.
$.paths[*][get,post,put,patch,delete]
warn
theneo-responses-401-defined
All operations must define a 401 response.
$.paths[*][get,post,put,patch,delete].responses
warn
theneo-request-body-content-type
POST/PUT/PATCH request bodies must declare application/json or multipart/form-data content type.
$.paths[*][post,put,patch].requestBody.content
error
theneo-project-id-path-param
Paths with {projectId} must document the parameter in-path with required=true.
$.paths[*][get,post,put,patch,delete].parameters[?(@.name == 'projectId')]
warn
theneo-no-empty-descriptions
All operations must have a non-empty description.
$.paths[*][get,post,put,patch,delete]
warn
theneo-response-schema-defined
All 200/201 responses must define a schema.
$.paths[*][get,post,put,patch,delete].responses[200,201].content