Sorry · API Governance Rules
Sorry API Rules
Spectral linting rules defining API design standards and conventions for Sorry.
12 Rules
error 3
warn 7
info 2
Rule Categories
sorry
Rules
info
sorry-nested-resource-pattern
Sorry API uses /pages/{page_id}/... nested resource pattern
$.paths
warn
sorry-operation-summary-title-case
Operation summaries must use Title Case
$.paths[*][get,post,put,patch,delete].summary
error
sorry-operation-id-required
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
sorry-operation-id-camel-case
OperationId must use camelCase convention
$.paths[*][get,post,put,patch,delete].operationId
warn
sorry-operation-has-tags
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
error
sorry-post-has-request-body
POST and PATCH operations must define a requestBody
$.paths[*][post,patch]
warn
sorry-401-response
All operations must document a 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
warn
sorry-delete-returns-204
DELETE operations should return 204 No Content
$.paths[*].delete.responses
warn
sorry-tags-title-case
All tags in the spec must use Title Case
$.tags[*].name
info
sorry-rate-limit-documented
API info should mention rate limiting (10 req/s)
$.info
error
sorry-security-defined
Bearer auth security must be defined
$
warn
sorry-response-schema-defined
Successful responses must define a JSON schema
$.paths[*][get,post,patch].responses['200','201'].content['application/json']