Sentry · API Governance Rules
Sentry API Rules
Spectral linting rules defining API design standards and conventions for Sentry.
13 Rules
error 5
warn 7
info 1
Rule Categories
sentry
Rules
warn
sentry-paths-trailing-slash
Sentry API paths must end with a trailing slash
$.paths[*]~
error
sentry-operation-id-required
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
sentry-operation-id-camel-case
Sentry operationIds use camelCase (listIssues, createRelease, etc.)
$.paths[*][get,post,put,patch,delete].operationId
error
sentry-operation-summary-required
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
warn
sentry-operation-description-required
All operations must have a description
$.paths[*][get,post,put,patch,delete]
error
sentry-operation-tags-required
All operations must be tagged
$.paths[*][get,post,put,patch,delete]
warn
sentry-valid-tags
Operations must use tags from the defined tag list
$.paths[*][get,post,put,patch,delete].tags[*]
warn
sentry-org-slug-ref
organization_slug path parameter should use $ref to the shared parameter definition
$.paths[*][get,post,put,patch,delete].parameters[?(@.name=='organization_slug')]
info
sentry-list-operations-pagination
GET operations returning arrays should include cursor and limit pagination parameters
$.paths[*].get
warn
sentry-parameter-description
All parameters must have descriptions
$.paths[*][get,post,put,patch,delete].parameters[*]
error
sentry-response-success-required
Operations must define at least one success response (200 or 201)
$.paths[*][get,post,put,patch,delete].responses
error
sentry-security-defined
Sentry API requires authentication on all endpoints
$
warn
sentry-components-schemas-defined
API must define reusable schemas in components
$.components