specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Sportradar
providerId: sportradar
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Data
  - Sports Data
  - Media
  - Rate Limiting
description: Sportradar does not publish a consolidated rate-limits page. Trial
  keys are commonly capped at low QPS, and commercial limits are negotiated per
  contract and per sport feed. Real-time push feeds use streaming rather than
  per-second polling.
sources:
  - https://sportradar.com/
  - https://docs.sportradar.com/
notes: Per-second / per-minute caps are not publicly documented; published only
  inside the developer portal once a key is provisioned.
responseCodes:
  throttled: 429
limits:
  - name: Trial Key (per sport package)
    scope: key
    metric: requests_per_second
    limit: see developer portal
    notes: Trial / sandbox keys are typically capped at low QPS (often 1 QPS) per
      sport package; the exact value is shown in the developer portal once
      issued.
  - name: Commercial License Limits
    scope: contract
    metric: varies
    limit: see commercial agreement
    notes: Throughput, polling intervals, and concurrent stream counts are
      contractually defined per sport, region, and use case.
policies:
  - name: Trial vs Production
    description: Trial keys exist primarily for evaluation. Production throughput
      is unlocked under a commercial license.
  - name: Push vs Pull
    description: Real-time data is delivered via push streams; clients should not
      poll at high frequency in lieu of subscribing to the appropriate stream.
maintainers:
  - FN: API Evangelist
    email: info@apievangelist.com