Unum · API Governance Rules
Unum API Rules
Spectral linting rules defining API design standards and conventions for Unum.
10 Rules
warn 10
Rule Categories
unum
Rules
warn
unum-operation-ids-camel-case
Operation IDs must use camelCase
$.paths[*][*].operationId
warn
unum-path-kebab-case
Path segments must use kebab-case
$.paths[*]~
warn
unum-require-group-id
Collection endpoints should require groupId query parameter for multi-tenant isolation
$.paths[?([email protected](/{.*}/))].get
warn
unum-require-pagination
List operations must support pagination parameters
$.paths[*].get
warn
unum-dates-iso8601
Date fields should use ISO 8601 format
$.components.schemas[*].properties[?(@.type == 'string')]
warn
unum-response-envelope
List responses should use a data envelope with pagination metadata
$.paths[*].get.responses.200.content.application/json.schema
warn
unum-error-schema
Error responses must use consistent error schema with code and message
$.paths[*][*].responses[?(@property >= '400')].content.application/json.schema
warn
unum-oauth2-security
All paths must declare OAuth2 security
$.paths[*][get,post,put,delete]
warn
unum-operation-summaries-title-case
Operation summaries must use Title Case
$.paths[*][*].summary
warn
unum-tags-defined
All operation tags must reference tags defined in the top-level tags array
$.paths[*][*].tags[*]