Suger · API Governance Rules
Suger API Rules
Spectral linting rules defining API design standards and conventions for Suger.
9 Rules
error 3
warn 6
Rule Categories
suger
Rules
error
suger-org-scoped-paths
All Suger API paths must be scoped to an organization via /org/{orgId}
$.paths
warn
suger-operation-id-pascal-case
Suger operationIds must use PascalCase
$.paths[*][*].operationId
error
suger-operation-summary-required
All Suger API operations must have a summary
$.paths[*][get,post,put,patch,delete]
warn
suger-operation-tags-required
All Suger API operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
error
suger-operation-id-required
All Suger API operations must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
suger-security-api-key
Suger API uses APIKeyAuth - all operations must declare security
$.paths[*][get,post,put,patch,delete]
warn
suger-path-param-camel-case
Suger path parameters should use camelCase naming
$.paths[*][*].parameters[?(@.in == 'path')].name
warn
suger-request-body-json
Suger request bodies should use application/json content type
$.paths[*][post,put,patch].requestBody.content
warn
suger-response-schema-defined
Suger API 200 responses should have a schema defined
$.paths[*][get,post,put,patch].responses['200'].content