Browse Sports, Leagues, and Matches with Sportrix Data

The Sportrix Data fixture catalog lets you navigate from sports down to individual matches. All catalog endpoints require the fixtures scope. Your client is configured with an allowlist of enabled sports — you’ll only ever see data for those sports, and requests outside your allowlist return empty results rather than errors.

List your enabled sports

Start by fetching the sports your account can access. GET /sports returns a plain array (not paginated) because the list is small and bounded.

curl https://api.sportrixdata.com/api/sports \
  -H "X-API-Key: $KEY"

[{ "id": 1, "name": "Soccer" }]

Note the id — you’ll use it as the sport parameter in every subsequent request. Requesting data for a sport ID that isn’t in this list is not an error; it simply returns an empty result.

List leagues for a sport

Pass the sport ID to GET /leagues to retrieve all leagues available under that sport. Results are returned in a pagination envelope.

curl "https://api.sportrixdata.com/api/leagues?sport=1" \
  -H "X-API-Key: $KEY"

{
  "items": [{ "id": 172, "name": "USA USL W-League Women" }],
  "total": 1,
  "limit": 100,
  "offset": 0,
  "count": 1,
  "page": 1,
  "total_pages": 1,
  "has_more": false
}

To page through a large result set, increase offset by limit on each request until has_more is false. The maximum page size is 200; values above that are clamped automatically.

Filter to active leagues only

If you only want leagues that have something happening right now or soon, use GET /leagues/active. It returns the same pagination envelope as /leagues, but only includes leagues with at least one NOT_STARTED or STARTED match.

curl "https://api.sportrixdata.com/api/leagues/active?sport=1" \
  -H "X-API-Key: $KEY"

This is useful for building a live dashboard — skip the leagues with no activity rather than iterating the full list.

List matches for a league

With a league ID in hand, fetch its matches using GET /matches. The league parameter is required.

curl "https://api.sportrixdata.com/api/matches?league=172" \
  -H "X-API-Key: $KEY"

Each item in the response is a match object:

{
  "id": 41301,
  "home_team": "Salmon Bay FC (W)",
  "away_team": "West Seattle Rhodies FC (W)",
  "start_time": "2026-06-18T02:00:00Z",
  "status": "NOT_STARTED"
}

The match id is what you’ll use when calling /live, /result, or subscribing via WebSocket.

Filter matches by status

Add the status parameter to narrow results to one phase of play. The three valid values are NOT_STARTED, STARTED, and FINISHED.

curl "https://api.sportrixdata.com/api/matches?league=172&status=STARTED" \
  -H "X-API-Key: $KEY"

Matches that the data provider has marked as suspended or postponed are never returned by any catalog endpoint. They are filtered out before your request is answered.

Filter matches by date range

Use start_after and start_before to restrict results to a window of scheduled kick-off times. Both parameters accept ISO 8601 timestamps in UTC.

curl "https://api.sportrixdata.com/api/matches?league=172&start_after=2026-06-18T00:00:00Z&start_before=2026-06-19T00:00:00Z" \
  -H "X-API-Key: $KEY"

You can combine date filters with a status filter in the same request.

Get a single match

Once you know a match ID, retrieve it directly with GET /matches/{id}.

curl "https://api.sportrixdata.com/api/matches/41301" \
  -H "X-API-Key: $KEY"

This returns the match object directly (not inside a pagination envelope). A 404 is returned if the match doesn’t exist, is in a sport outside your allowlist, or has been suspended or postponed.