SportriX API Review 2026

SportriX is a real-time sports data API that covers live scores, play-by-play events, stats, and standings across 7 sports and 3,000+ leagues. It also exposes a Pinnacle odds passthrough, which puts pricing data alongside match state in the same platform. You authenticate with an X-API-Key header, hit REST endpoints at api.sportrix.ai, and subscribe to a WebSocket stream at wss://scores.sportrix.ai/v1/stream for push updates.

The combination of live scoring data and sportsbook odds in one feed is unusual. Most providers sell one or the other. SportriX tries to sell both, though the odds layer is limited to Pinnacle rather than a broad aggregation. If you need a sharp-book reference price next to in-play match state, that pairing has a clear use case. If you need odds from 40 sportsbooks, look at the sports odds API directory instead.

Seven sports are listed for stats: soccer, basketball, ice hockey, cricket, tennis, football, and volleyball. The American football feed covers the NFL and college football (NCAAF), and the Pinnacle odds on the Elite plan cover nine sports, adding baseball, esports and MMA. The site claims 3,000+ leagues and competitions, and the API scopes access per sport and league through a granular permissions system.

Within each sport the data model adjusts. Soccer matches return clock, phase, stats, and events. Cricket matches return innings score, batsmen, bowler, and current over. Each sport gets a tailored live snapshot rather than a generic score object, which matters if you are building sport-specific UIs.

Available data types include:

• Live scores with sub-second event delivery (the site targets 22ms p90 latency).
• Play-by-play events: shots, cards, substitutions, and other structured actions.
• Stats: player, team, lineup, and situational metrics.
• Schedules, standings, and rosters.
• Pinnacle odds: a passthrough feed with prices, market names, betting cutoffs, and stake limits.

Box scores and historical data are marked as unverified in the directory. The docs do not describe a historical archive endpoint, so assume you will need a separate source for backtesting. See the historical odds guide if that matters to your project.

The odds layer lives under /v1/pinnacle/ and passes through Pinnacle's own data. Endpoints cover sports, leagues, matches, and odds. The odds endpoint returns every current selection for a match with prices, market names, betting cutoffs, and stake limits.

A separate WebSocket stream at wss://passthrough.sportrix.ai/v1/pinnacle/data delivers live price updates using delta messages keyed by market version. You apply each delta on top of the last snapshot, which keeps bandwidth low and lets you reconstruct the full state at any point.

This is not a multi-book aggregation. You get Pinnacle and nothing else. For a model that uses Pinnacle as its fair-value anchor and gets soft-book prices from a different feed, that single-source design works well. For line shopping across dozens of books, it does not.

SportriX has no free tier, but every plan starts with a 7-day free trial that needs a payment method, and the pricing page posts the full price list (checked November 2026). Plans run from $99 a month for stats on one sport to $1,199 for Elite, and enterprise starts at $3,000 a month. Plan names and the sports in each plan are posted, but rate limits are not.

Unpublished pricing is common at the enterprise end of the sports data market, so a posted price list and a trial make SportriX easier to evaluate than many feeds at this level. You can compare cost against the providers in the sports data API space that also publish full rate cards before you talk to anyone. Rate limits are the exception: the docs post none, so ask support what your plan allows.

The API docs do reference scope-based access control (fixtures, live_scores, live_scores_statistics, final_scores, odds), so each key gets a specific set of permissions. The posted plans follow the same split, with stats and Pinnacle odds sold apart and priced by sport.

SportriX sells access from its pricing page. Pick a plan and start the 7-day free trial; the page says you get your API key that day. The trial needs a payment method, each customer gets one, and billing begins on day 8 unless you cancel from your account page. Plans run from $99 a month for stats on one sport and $299 for Pinnacle odds on one sport, up to the $799 Pro and $1,199 Elite bundles, with enterprise from $3,000 (checked November 2026).

The quickstart in the docs still says the SportriX team issues keys, so if yours does not arrive, email support@sportrix.ai. Keys start with sk_ and go in the X-API-Key header on every call except GET /health. The WebSocket also accepts the key as a ?key= parameter.

This sample calls GET /sports on the REST base URL https://api.sportrix.ai/api, with the key in X-API-Key (from the docs, checked November 2026).

import os

import requests

resp = requests.get(
    "https://api.sportrix.ai/api/sports",
    headers={"X-API-Key": os.environ["SPORTRIX_API_KEY"]},
    timeout=10,
)
resp.raise_for_status()

for sport in resp.json():
    print(sport["id"], sport["name"])

You get back only the sports enabled on your key, each as an object with an id and a name, such as {"id": 1, "name": "Soccer"}. Pass an id as the sport parameter of GET /leagues to list that sport's leagues, which come back in a paging envelope with items, total and has_more. Ask about a sport outside your plan and you get an empty list, not an error. Leagues need the fixtures scope, so a 403 means your key lacks it.

The SportriX docs publish no request-rate numbers for REST or the WebSocket, so ask support@sportrix.ai what your plan allows (checked November 2026). Errors are plain: 401 for a missing, disabled or expired key, 403 for a key without the scope an endpoint needs, 404 for a sport outside your allowlist, and 422 for a bad parameter, each with a JSON detail field. List endpoints page with limit (default 100, maximum 200) and offset. The server pings the WebSocket every 30 seconds, so keep your client timeout above that.

The docs run on Mintlify, with an llms.txt index, curl and Python examples, and a separate section for the Pinnacle passthrough. We found no SDK, OpenAPI file, changelog or status page. GET /health answers without a key if you want a liveness check. For push-delivery tradeoffs, see our live sports odds API guide.

The product targets two overlapping audiences:

• Sportsbooks and trading desks that need live match state and a sharp-book reference price in one feed. The Pinnacle passthrough paired with sub-second scoring events is the specific value here.
• Media and data platforms that want live scores, play-by-play, and standings across multiple sports with sport-specific data models.

It is a harder sell for solo developers or small projects. Signup is self-serve with a 7-day trial, but the trial needs a card, and with no published rate limits you ask support what a plan allows before you size a build. Developers building hobby projects or MVPs will find faster onboarding elsewhere.

SportriX occupies a niche: live scoring plus Pinnacle odds in one platform. Most sports data APIs (SportsData.io, ESPN feeds, open stat sources) handle scores and stats but carry no odds. Most odds APIs aggregate multiple books but carry no scoring data. SportriX bridges the two, which reduces the number of vendors you integrate.

The tradeoff is breadth. Seven sports is a narrow roster compared to providers covering 30 or more. The odds layer covers one book, not hundreds. And with no free tier and no published rate limits, evaluation takes more steps than at competitors that hand you a free key in seconds.

If you already have a scoring feed and need broad odds, an aggregator from the directory is a better fit. If you already have odds and need scores, an open data source or a dedicated stats provider may cost less. SportriX makes sense when you specifically want both in one integration and Pinnacle is the book you care about.

SportriX combines live scoring with a Pinnacle odds passthrough in a single API, and the sub-second latency targets and sport-specific data models suggest a serious infrastructure behind it. The WebSocket streams for both scores and odds are well-documented, and the scope-based access control is a nice detail for teams that need to isolate permissions.

The gaps are rate limits and history. The docs publish no rate limits, the free trial lasts 7 days and needs a card, and claims around box scores and historical data stay unverified. For a team with budget and a clear need for Pinnacle-anchored match state, it is worth a trial. For everyone else, the evaluation cost is higher than it needs to be. Start the trial through sportrix.ai and test the WebSocket feed against a live match before billing starts.

Last updated: 2 November 2026 · How providers get listed