Sportradar · API Governance Rules
Sportradar API Rules
Spectral linting rules defining API design standards and conventions for Sportradar.
12 Rules
error 4
warn 5
info 3
Rule Categories
sportradar
Rules
error
sportradar-operation-id-required
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete,head,options]
warn
sportradar-operation-id-verb-prefix
operationId must start with a standard REST verb (get, list, create, update, delete).
$.paths[*][get,post,put,patch,delete].operationId
warn
sportradar-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
warn
sportradar-tags-required
Every operation must have at least one tag.
$.paths[*][get,post,put,patch,delete]
error
sportradar-api-key-auth-required
API must define apiKey security scheme.
$.components.securitySchemes
error
sportradar-response-200-required
Every operation must define a 200 success response.
$.paths[*][get,post,put,patch,delete].responses
warn
sportradar-401-response-required
Every operation must define a 401 Unauthorized response.
$.paths[*][get,post,put,patch,delete].responses
info
sportradar-429-rate-limit-response
Every operation should define a 429 Too Many Requests response.
$.paths[*][get,post,put,patch,delete].responses
info
sportradar-path-sport-prefix
Paths should include sport or competition prefix (e.g., /nba/, /nfl/, /soccer/).
$.paths
info
sportradar-json-response-suffix
Sportradar endpoints use .json suffix for JSON responses.
$.paths
error
sportradar-servers-required
The API must define at least one server.
$
warn
sportradar-info-contact-required
The info object must include a contact entry.
$.info