Unleash · API Governance Rules
Unleash API Rules
Spectral linting rules defining API design standards and conventions for Unleash.
8 Rules
error 1
warn 4
info 3
Rule Categories
unleash
Rules
info
unleash-admin-path-prefix
Admin API paths must start with /api/admin/
$.paths[*]~
warn
unleash-title-case-summary
Operation summaries must use Title Case
$.paths[*][*].summary
warn
unleash-operation-tags
All operations must have at least one tag
$.paths[*][*]
error
unleash-operation-id
All operations must have an operationId
$.paths[*][*]
info
unleash-auth-header
Admin API operations must require Authorization header
$.paths[/api/admin*][*]
info
unleash-feature-project-scope
Feature flag paths should be scoped under /projects/{projectId}/
$.paths[/api/admin/features*]~
warn
unleash-not-found-response
Resource endpoints should define 404 responses
$.paths[*][get,delete,put,patch]
warn
unleash-unauthorized-response
Protected operations should define 401 responses
$.paths[/api/admin*][*]