Skip to main content

SportScore API Terms of Use

Last updated: 23 April 2026 · Questions? [email protected]

Jump to: Free tier · Attribution requirement · Rate limits · Paid / commercial · Acceptable use · Liability

1. Free tier — what you get

The SportScore public API (endpoints under /api/widget/) is free to use under the terms on this page. No API key is required. CORS is open. Responses are JSON. Data covers football, basketball, cricket and tennis: live scores, fixtures, standings, top scorers, brackets and player statistics.

If your use of the API fits the profile below, you qualify for the free tier:

  • Personal projects, hobby sites, learning exercises
  • Open-source applications (source available on a public repository)
  • Non-commercial community tools, fan sites, Discord/Telegram bots
  • Early-stage commercial projects that display the attribution badge (see section 2)

2. Attribution requirement

The free tier is ad-free, key-free and rate-limit-generous because of a single condition: you display a visible "Powered by SportScore" link on every page, screen or surface that renders data sourced from our API.

2.1 Exact badge

Copy the snippet below into your footer, data panel, or an equivalently visible location. The rel="dofollow" attribute is required — nofollow, ugc and sponsored are not acceptable substitutes.

<a href="https://sportscore.com/" rel="dofollow" title="Sports data by SportScore"> Powered by SportScore </a>

2.2 Acceptable variants

You may adapt the visual styling (font, colour, icon) as long as the link remains a real HTML <a> element, discoverable by crawlers, and not obscured by CSS. Acceptable anchor-text variants:

  • Powered by SportScore (default)
  • Data by SportScore
  • Sports data: SportScore
  • SportScore (bare brand mention inside a sentence)

2.3 Not acceptable

  • rel="nofollow", rel="ugc", rel="sponsored", or any robots-style block that hides the link from search engines
  • Rendering the badge in a colour matched to the background, at font-size: 0, opacity: 0, or otherwise visually hidden
  • Loading the badge inside an iframe that crawlers cannot follow, or behind a client-side-only render that bots don't execute
  • Placing the badge on a page that uses our data, but linking from a different page that doesn't
  • Stripping the title attribute or replacing the href with a redirect that cloaks the destination
Short version: a real, visible, crawlable, dofollow link to https://sportscore.com/ on every page that uses our data. If you don't want to ship that badge, that's fine — section 4 covers the paid tier.

3. Rate limits & fair use

Free tier:

  • Approximately 1,000 requests per 24 hours per IP, with burst tolerance for reasonable spikes
  • Responses are edge-cached for 60 seconds — aim to cache on your side too
  • No service-level agreement (SLA). Data is provided as-is
  • We reserve the right to throttle or block clients that degrade service for others (e.g. uncached 10+ req/sec scraping)

Need higher limits, an SLA, or a dedicated endpoint? See section 4.

The paid tier is for situations where the free tier doesn't fit — typically:

  • Commercial applications that cannot ship the attribution badge (white-label products, internal B2B tools, paid apps with strict UI constraints)
  • Projects that exceed ~1,000 requests per 24 hours per IP
  • Deployments that require an SLA, custom endpoints, or historical-data access beyond the public API

Contact [email protected] with a short description of your use case, expected traffic, and whether you need attribution removal, higher limits, or both. Most commercial deals close in under a week.

5. Acceptable use

You may:

  • Cache API responses in your own infrastructure
  • Combine SportScore data with other sources in derived products (dashboards, alerts, analytics)
  • Build and monetise applications on top of the API (free tier requires the badge; paid tier does not)
  • Write and publish technical content, tutorials, or code samples referencing SportScore

You may not:

  • Scrape, mirror, or rehost raw API responses as a competing sports-data feed
  • Redistribute bulk datasets (e.g. dumping fixture tables into a public data marketplace)
  • Use the API to power tools that facilitate match-fixing, illegal gambling jurisdictions, or any activity prohibited by the laws of your or our jurisdiction
  • Misrepresent the source of the data (e.g. claim SportScore data as your own proprietary feed)
  • Evade rate limits by rotating IPs, proxies, or client identifiers

6. Data accuracy

We pull from a range of upstream providers and normalise the output. We aim for accuracy but cannot guarantee it — scorelines, player stats and fixture times can and do change after publication. Do not use the API as the sole source of truth for anything financial, legal, or safety-critical.

7. Liability & warranty

The API is provided "as is", without warranty of any kind, express or implied. SportScore is not liable for any direct, indirect, incidental, or consequential damages arising from your use or inability to use the API, including but not limited to lost profits, data loss, or service interruption.

8. Changes to these terms

We may update these terms. Material changes will be announced on this page with a new "Last updated" date, and — where possible — via email to API users we can contact. Continued use of the API after changes means you accept the updated terms.

9. Contact

Technical questions, commercial licensing, abuse reports, takedown requests: [email protected].

Back to the developer portal.