Vibes Platform · API Governance Rules
Vibes Platform API Rules
Spectral linting rules defining API design standards and conventions for Vibes Platform.
13 Rules
error 2
warn 11
Rule Categories
vibes
Rules
warn
vibes-company-key-path-required
All Vibes Platform API paths must include the company_key path parameter.
$.paths[*]
warn
vibes-operationid-camel-case
Operation IDs must use camelCase naming.
$.paths[*][*].operationId
warn
vibes-operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][*].summary
error
vibes-response-200-or-201-required
Every operation must have a 200 or 201 success response.
$.paths[*][get,post,put,patch]
warn
vibes-401-response-required
All operations must include a 401 Unauthorized response.
$.paths[*][get,post,put,patch,delete].responses
warn
vibes-429-response-required
All operations must include a 429 Too Many Requests response.
$.paths[*][get,post,put,patch,delete].responses
error
vibes-basic-auth-security
Vibes Platform APIs use HTTP Basic authentication.
$.components.securitySchemes
warn
vibes-request-body-json
POST and PUT request bodies must use application/json content type.
$.paths[*][post,put].requestBody.content
warn
vibes-response-json-content
Success responses must return application/json content.
$.paths[*][*].responses[200,201].content
warn
vibes-no-trailing-slash
API paths must not have trailing slashes.
$.paths[*]~
warn
vibes-path-kebab-case
Path segments must use lowercase kebab-case.
$.paths[*]~
warn
vibes-operation-description-required
All operations must have a description.
$.paths[*][get,post,put,patch,delete]
warn
vibes-tag-required
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete].tags