Scispot · API Governance Rules
Scispot API Rules
Spectral linting rules defining API design standards and conventions for Scispot.
13 Rules
error 2
warn 9
info 2
Rule Categories
scispot
Rules
error
scispot-apikey-auth-defined
Scispot API must use API key authentication via apiKey header
$.components.securitySchemes.*.type
warn
scispot-operation-id-camel-case
Operation IDs must use camelCase naming convention
$.paths.*.*.operationId
warn
scispot-path-kebab-case
API paths must use kebab-case segments
$.paths[*]~
warn
scispot-post-returns-201
POST endpoints that create resources must return 201 Created
$.paths.*.post.responses
warn
scispot-delete-returns-204
DELETE endpoints must return 204 No Content on success
$.paths.*.delete.responses
warn
scispot-auth-401-response
All authenticated endpoints must define a 401 Unauthorized response
$.paths.*.*.responses
warn
scispot-single-resource-404
Single-resource retrieval endpoints must define 404 response
$.paths[*][?(@property == 'get')].responses
error
scispot-post-put-require-body
POST and PUT endpoints must define a request body
$.paths.*[post,put]
warn
scispot-operation-description
All operations must have a description
$.paths.*.*
warn
scispot-operation-tags
All operations must be tagged
$.paths.*.*
info
scispot-list-pagination-params
List endpoints should support page and limit pagination parameters
$.paths.*.get.parameters[*].name
warn
scispot-server-versioned
Server URL must include API version prefix
$.servers[*].url
info
scispot-use-component-schemas
Response bodies should reference component schemas rather than inline definitions
$.paths.*.*.responses.*.content.*.schema