Sumo Logic · API Governance Rules
Sumo Logic API Rules
Spectral linting rules defining API design standards and conventions for Sumo Logic.
9 Rules
error 2
warn 5
info 2
Rule Categories
sumo
Rules
warn
sumo-logic-versioned-paths
Sumo Logic API paths must be versioned with /v1/ or /v2/
$.paths
error
sumo-logic-operation-summary-required
All Sumo Logic operations must have a summary
$.paths[*][get,post,put,patch,delete]
error
sumo-logic-operation-id-required
All Sumo Logic operations must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
sumo-logic-operation-id-camel-case
Sumo Logic operationIds should use camelCase
$.paths[*][*].operationId
warn
sumo-logic-basic-auth
Sumo Logic uses Basic authentication (accessId:accessKey)
$.components.securitySchemes
warn
sumo-logic-operation-tags-required
All Sumo Logic operations must be tagged
$.paths[*][get,post,put,patch,delete]
info
sumo-logic-error-response-code
Sumo Logic error responses should include errorCode
$.components.schemas[?(@.properties.errorCode)]
warn
sumo-logic-get-response-schema
Sumo Logic GET operations should have a 200 response schema
$.paths[*].get.responses['200']
info
sumo-logic-pagination-limit
Sumo Logic uses 'limit' for pagination page size
$.paths[*][*].parameters[?(@.name == 'pageSize' || @.name == 'count')]