> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sportrix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Sportrix Data – Live Scores and Fixtures REST API

> Sportrix Data provides programmatic access to sports fixtures, live scores, statistics, and final match results via REST API and WebSocket stream.

Sportrix Data gives you programmatic access to a **sports fixture catalog**, **real-time live scores and statistics**, and **post-match results**. Whether you're building a live score widget, a match-tracking dashboard, or a data pipeline, Sportrix Data provides the structured, low-latency data feed you need.

## Two delivery surfaces

Sportrix Data exposes two complementary interfaces — use one or both depending on your use case.

### REST API

**Base URL:** `https://api.sportrixdata.com/api`

The REST API is the starting point for every integration. Use it to browse your enabled sports, discover leagues and fixtures, and fetch on-demand live or final score snapshots for any match. All REST paths in this documentation are relative to this base URL.

### WebSocket stream

**Endpoint:** `wss://scores.sportrixdata.com/v1/stream`

The WebSocket stream pushes real-time live scores and statistics to your connection as match state changes — no polling required. After subscribing to a match you immediately receive a full snapshot, followed by incremental updates for the duration of the match.

## Scopes

Every API key carries one or more **scopes** that control which endpoints it can reach. There are four scopes available to customers:

| Scope                    | What it unlocks                                                       |
| ------------------------ | --------------------------------------------------------------------- |
| `fixtures`               | Browse sports, leagues, and matches                                   |
| `live_scores`            | On-demand live score snapshots (`GET /matches/{id}/live`)             |
| `live_scores_statistics` | Real-time WebSocket stream **and** `GET /matches/{id}/live`           |
| `final_scores`           | Half-time and full-time result snapshots (`GET /matches/{id}/result`) |

<Note>
  `GET /matches/{id}/live` accepts either `live_scores` **or** `live_scores_statistics`. The WebSocket stream requires `live_scores_statistics` specifically — `live_scores` alone is not sufficient to connect.
</Note>

See [Scopes](/concepts/scopes) for a full breakdown of which endpoints each scope gates.

## Sport allowlisting

Your account is configured with a set of **enabled sports**. Access is deny-by-default: you only ever see sports, leagues, and matches for the sports on your allowlist. Requesting data outside your allowlist is not an error — it simply returns an empty result set (for example, `GET /leagues?sport=<unavailable>` returns `[]`). Contact support to adjust your enabled sports.

<Info>
  Your enabled sports are reflected in the response to `GET /sports`, which lists only the sports your key can access.
</Info>

## Where to go next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="bolt" href="/quickstart">
    Make your first REST call and connect to the WebSocket stream in under five minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Learn how to pass your API key and handle auth errors.
  </Card>

  <Card title="REST API Overview" icon="code" href="/api/overview">
    Explore every endpoint, request parameter, and response shape.
  </Card>

  <Card title="WebSocket Overview" icon="signal-stream" href="/api/websocket-overview">
    Understand the WebSocket protocol, frames, and subscription lifecycle.
  </Card>
</CardGroup>