Saasment · API Governance Rules
Saasment API Rules
Spectral linting rules defining API design standards and conventions for Saasment.
9 Rules
error 2
warn 5
info 2
Rule Categories
saasment
Rules
warn
saasment-operation-summary-title-case
All operation summaries must use Title Case
$.paths[*][*].summary
error
saasment-security-bearer-required
All endpoints except public must require BearerAuth security
$.paths[*][*]
warn
saasment-operation-ids-kebab-case
Operation IDs should use camelCase
$.paths[*][*].operationId
warn
saasment-tags-required
All operations must have at least one tag
$.paths[*][*]
error
saasment-response-200-defined
All operations must define a success response
$.paths[*][get,put,patch].responses
warn
saasment-error-responses-defined
Operations should define 401 unauthorized response
$.paths[*][get,post,put,patch,delete].responses
info
saasment-pagination-parameters
List endpoints should support pagination with page and per_page
$.paths[*][get]
warn
saasment-severity-enum
Severity fields should use standard enum values
$.components.schemas..properties.severity
info
saasment-resource-ids-as-strings
Resource ID fields should be string type for UUID compatibility
$.components.schemas..properties.id