SailPoint · API Governance Rules
SailPoint API Rules
Spectral linting rules defining API design standards and conventions for SailPoint.
10 Rules
error 3
warn 6
Rule Categories
sailpoint
Rules
warn
sailpoint-operation-id-camel-case
OperationIds must use camelCase (SailPoint convention).
$.paths[*][*].operationId
error
sailpoint-summary-not-empty
All operations must have a summary.
$.paths[*][*]
warn
sailpoint-tags-required
All operations must have at least one tag.
$.paths[*][*]
error
sailpoint-response-200-required
All operations must define a 200 or 201 response.
$.paths[*][*].responses
warn
sailpoint-error-responses-required
Operations should define standard SailPoint error responses (400, 401, 403, 404, 429, 500).
$.paths[*][*].responses
warn
sailpoint-path-kebab-case
Paths must use kebab-case for multi-word segments.
$.paths[*]~
warn
sailpoint-oauth2-security
All operations should declare OAuth2 or PAT security.
$.paths[*][*]
hint
sailpoint-list-operations-pagination
List operations should support limit and offset query parameters.
$.paths[*].get
error
sailpoint-no-trailing-slash
Paths must not have trailing slashes.
$.paths[*]~
warn
sailpoint-content-type-json
Request bodies should use application/json content type.
$.paths[*][*].requestBody.content