Stats Perform · API Governance Rules
Stats Perform API Rules
Spectral linting rules defining API design standards and conventions for Stats Perform.
8 Rules
error 3
warn 3
Rule Categories
stats
Rules
error
stats-perform-api-key-required
Stats Perform STATS API requires an API key passed as "api_key" query parameter for all authenticated endpoints.
$.paths[*][*]
warn
stats-perform-path-sport-prefix
Stats Perform paths follow a consistent structure: /stats/{sport}/{leaguePath}/... or /editorial/{sport}/{leaguePath}/... The sport path parameter must be one of the defined sport types.
$.paths[?(@ =~ /^\/stats\/|^\/editorial\//)]
warn
stats-perform-operation-ids-camel-case
Stats Perform API operation IDs use camelCase naming convention.
$.paths[*][*].operationId
warn
stats-perform-summaries-title-case
All Stats Perform API operation summaries must use Title Case.
$.paths[*][*].summary
error
stats-perform-tags-required
Every Stats Perform API operation must have at least one tag for proper documentation grouping.
$.paths[*][*]
hint
stats-perform-api-results-wrapper
Stats Perform API list responses typically wrap their data in an "apiResults" array. List operation responses should follow this pattern.
$.paths[?(@ =~ /\/$/)]..responses['200'].content['application/json'].schema.properties
error
stats-perform-case-sensitive-paths
Stats Perform path segments are case-sensitive. Decode endpoint paths such as /decode/networkTypes/ use camelCase. All path segments must match the documented casing exactly.
$.paths
hint
stats-perform-event-status-values
Stats Perform uses consistent event status values across all sports.
$.components.schemas[*].properties.status.enum