Raygun · API Governance Rules
Raygun API Rules
Spectral linting rules defining API design standards and conventions for Raygun.
11 Rules
error 1
warn 8
info 2
Rule Categories
raygun
Rules
warn
raygun-info-title-required
API title must reference Raygun.
$.info
error
raygun-server-base-uri
Raygun Public API server must point at https://api.raygun.com/v3.
$.servers[*]
warn
raygun-summary-title-case
Every operation summary should use Title Case.
$.paths.*[get,put,post,delete,patch].summary
warn
raygun-operation-id-kebab
operationId must be kebab-case.
$.paths.*[get,put,post,delete,patch].operationId
warn
raygun-resources-kebab-case
Path segments must use kebab-case (Raygun convention — e.g. /error-groups, /source-maps).
$.paths
warn
raygun-identifier-path-style
Resource identifiers must be referenced as {resource-identifier} (kebab-case curly placeholders).
$.paths
warn
raygun-security-bearer-required
Every protected operation must inherit the personal_access_token bearer scheme.
$.components.securitySchemes
info
raygun-problem-details-error-response
4xx responses should use the shared problem-details response component.
$.paths.*[get,put,post,delete,patch].responses.['400','401','403','404','409','422']
info
raygun-429-too-many-requests
Operations should document a 429 Too Many Requests response.
$.paths.*[get,put,post,delete,patch].responses
warn
raygun-no-trailing-slash
Paths must not end with a trailing slash.
$.paths
warn
raygun-tag-defined
Operations must declare at least one tag for organization.
$.paths.*[get,put,post,delete,patch]