Synatic · API Governance Rules
Synatic API Rules
Spectral linting rules defining API design standards and conventions for Synatic.
6 Rules
error 3
warn 2
info 1
Generated by API Evangelist
Written by API Evangelist tooling for Synatic's APIs. It is a starting point, not a ruleset Synatic publishes or enforces.
Rule Categories
operation
path
Rules
info
operation-has-summary
Every operation has a summary (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete]
error
operation-has-tags
Every operation is tagged (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete]
error
operation-has-success-response
Every operation declares a 2xx response (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete].responses
warn
operation-declares-4xx
Every operation declares at least one 4xx response (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete].responses
warn
operation-declares-401-or-403
Every operation declares 401 or 403 (measured: 100% of this contract)
$.paths[*][get,post,put,patch,delete].responses
error
path-no-trailing-slash
Paths carry no trailing slash (measured: 100% of this contract)
$.paths[*]~
Spectral Ruleset
Work with this as data
Every ruleset here is available over the APIs.io API and to AI agents over MCP.