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: soccer, basketball, ice hockey, cricket, tennis, football, and volleyball. 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.

The directory lists SportriX with a free tier, but the site does not publish pricing. Access requires contacting info@sportrix.ai or filling out a request form. The pricing range in the directory suggests mid to high cost (two to four price tiers), but exact plan names, rate limits, and per-sport scoping are negotiated rather than posted.

Unpublished pricing is common at the enterprise end of the sports data market, but it creates friction for developers who want to evaluate a feed before talking to sales. You cannot compare cost against competitors without a conversation first. If transparent pricing matters to you, several providers in the sports data API space publish full rate cards.

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. That suggests tiered plans, but the tiers are not public.

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. Contact-only pricing, no self-serve signup, and no published rate limits mean you invest time in a sales conversation before you see real data. 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 the lack of published pricing or self-serve keys makes evaluation slower than competitors that hand you a 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 transparency and accessibility. No published pricing, no self-serve signup, and unverified claims around box scores and historical data. For a team with budget and a clear need for Pinnacle-anchored match state, it is worth a conversation. For everyone else, the evaluation cost is higher than it needs to be. Request access through sportrix.ai and test the WebSocket feed against a live match before you commit.