Riverside · API Governance Rules
Riverside API Rules
Spectral linting rules defining API design standards and conventions for Riverside.
11 Rules
error 3
warn 4
info 4
Rule Categories
riverside
Rules
warn
riverside-operation-has-tag
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
error
riverside-operation-has-summary
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
error
riverside-operation-has-operation-id
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
riverside-api-key-auth
API should use Bearer/API key authentication
$.components.securitySchemes[*]
info
riverside-recording-id-path-param
Recording endpoints should use recording_id as path parameter
$.paths['/api/v1/recordings/{recording_id}'][*].parameters[?(@.in === 'path')]
error
riverside-responses-have-200
GET operations should have a 200 response
$.paths[*].get
warn
riverside-delete-returns-204
DELETE operations should return 204 No Content
$.paths[*].delete
info
riverside-pagination-uses-page
Paginated list endpoints should use page parameter
$.paths[*].get.parameters[?(@.name === 'page')]
info
riverside-schema-has-description
Schema components should have descriptions
$.components.schemas[*]
info
riverside-rate-limit-documented
Operations should document rate limiting in description
$.paths[*][get,post]
warn
riverside-versioned-paths
API paths should include version prefix (v1, v2, v3)
$.paths[*]~