OddiWire API Review 2026

OddiWire is an esports odds API. It takes the raw feed from ODDIN.GG, a Sportradar-backed esports odds provider, normalizes the market names and structures, and serves the result over REST and Server-Sent Events (SSE). It is not affiliated with ODDIN or Sportradar, and the site says so up front.

Two things stand out on first contact. The demo key is public: key=demo on any REST endpoint, no signup, and you're looking at live esports markets. And every selection carries a raw probability field, which is the provider's no-vig number. Most feeds give you a decimal price and leave you to back out the margin. OddiWire publishes both.

If you've seen PinnWire, the Pinnacle-focused feed from the same team, the design will feel familiar: same REST-plus-SSE shape, same key=demo onboarding, same permanent free tier. OddiWire applies that pattern to the esports odds vertical instead of Pinnacle lines.

The headline esports titles are CS2, League of Legends, Dota 2, and Valorant. We pulled live fixtures through the demo key and confirmed all four return markets. Beyond those, the feed carries eFootball, eBasketball, eCricket, King of Glory (KOG), Rainbow Six (R6), and CS2/Dota 2 Duels variants. eFootball alone had over 100 fixtures the day we tested, so the simulated-sport coverage runs deeper than many developers expect from an "esports" feed.

The health endpoint reports the full group discovery table. It showed active probes across additional sport keys (Tennis, Cricket, American Football, Aussie Rules, F1, Golf, and others). Whether those sport keys carry enough fixture volume to be useful depends on when you check and what ODDIN's board looks like that day.

Markets use a canonical naming layer. Ten Tier 1 keys (match_winner, main_handicap, main_total, team_total, first_period_winner, and five more) cover over half the open markets. Tier 2 and 3 keys exist for longer-tail markets, tagged as beta. Each market carries a structure field (exclusive, ladder, union, or partial) that tells you the arithmetic rules before you parse the selections.

Only tradeable (OPEN) markets come back by default. Add include=closed,suspended,resulted if you want the full picture, but a resulted selection never carries a price.

REST lives at /v1/. The main endpoints: /v1/fixtures returns a filtered fixture list with nested markets and selections; /v1/fixtures/:id pulls one event; /v1/counts gives live and prematch tallies by sport; /v1/health reports upstream connection status, market coverage, and the time since the last frame; /v1/me shows your plan, limits, and today's usage. The health and me endpoints don't count against your rate limit.

Auth works three ways, checked in order: an x-api-key header, a Bearer token, or a ?key= query parameter. The docs recommend headers since query strings end up in logs and referrers.

SSE lives at /v1/stream and pushes price updates in real time with a keepalive ping every 15 seconds. It's included on the Full plan only. This is Server-Sent Events over HTTP, not WebSocket. The practical difference: SSE is one-way (server to client), reconnection is built into the browser spec, and you don't need a WebSocket library. For a price feed that only flows downstream, SSE is a good fit.

Every selection in the response carries decimal price, fractional odds, and the raw probability. The /llms.txt file gives a machine-readable API reference, the same pattern PinnWire uses, so an AI coding assistant can read the docs and wire up the demo key in one pass.

Three self-serve tiers, plus a comparison card for direct ODDIN access:

• Free, $0: 100 REST calls per day, no SSE stream, no card required, forever. The public demo key (key=demo) is even lighter: 10 requests per 5 minutes, no signup at all.
• Basic, $29/mo: 5,000 REST calls per day. Still no SSE stream.
• Full, $299/mo: 30 REST calls per second, unlimited SSE with price-drop alerts.
• Direct Provider (comparison): $29,999/mo is what the compare page quotes for enterprise access to the ODDIN feed directly. It is a benchmark, not a plan OddiWire sells.

The compare page frames OddiWire against the direct-provider price, and the gap is striking: $299 versus $29,999 for the same underlying data, normalized and ready to use instead of raw. If your use case fits inside the self-serve tiers, that's the value proposition in one number.

Rate limits are enforced per key at second, minute, and day windows depending on the plan. A rejected request returns HTTP 429 with a Retry-After header and does not count against your other windows, so backing off correctly costs nothing.

OddiWire is one feed from one upstream provider. That scope is deliberate, and it shapes what you won't find:

• Multiple bookmakers. Every price comes from ODDIN. There's no per-book comparison, no line shopping, no named sportsbooks in the feed. Pair it with a multi-book aggregator from the API directory if you need cross-book coverage.
• Historical or closing odds. The feed covers live and upcoming fixtures. For backtesting or closing-line analysis, add a historical odds source.
• Futures, player props, same-game parlays, deeplinks. Markets are match-level: winner, handicaps, totals, map winners, and similar.
• Bet settlement. No general settlement endpoint. Markets carry a status field, but that's different from a settlement callback.
• Traditional sports depth. The health endpoint shows probes for tennis, cricket, football, and other sport keys, but the core coverage is esports and simulated sports. For NFL or Premier League lines, pair it with a traditional-sports feed from the directory.
• Stats or scores service. Live fixtures include a score object with phase breakdowns, but there's no standalone statistics endpoint.
• An MCP server. The /llms.txt reference is there, but no packaged MCP server exists today.

OddiWire is built for developers who want ODDIN esports odds without paying enterprise prices or building the delivery layer themselves:

• Esports odds dashboards. The canonical market keys and structure labels mean you can render a market card from the response shape without mapping each market name by hand.
• Alert and drop-detection systems. The SSE stream on the Full plan pushes price changes and drop alerts in real time, with the no-vig probability already attached.
• Simulated-sport coverage. eFootball and eBasketball carry heavy fixture volume around the clock, which is useful for products that need a constant stream of events.
• Prototypes and hobby projects. 100 free REST calls a day with no card is enough to build and demo an esports odds app without spending anything.

If you need multi-book line shopping, traditional sports, or historical data alongside the esports feed, OddiWire pairs well with a broader provider from the directory. Sharp esports prices from one feed, breadth from the other.

OddiWire does one thing well: it puts ODDIN.GG esports odds into a clean, documented REST and SSE API at a fraction of the direct-provider cost. The canonical market keys, the raw probability field, and the structure labels are real time-savers for developers who'd otherwise be mapping provider-specific naming by hand.

The demo key makes verification trivial. Append key=demo, read the JSON, and you'll know inside a minute whether the coverage and market depth fit your product. The permanent free tier means you can build against it before you pay anything.

Coverage is esports-first and single-provider. That's a clear shape and the team is upfront about it. If your project is esports odds, this is worth a serious look. If it's broader than that, treat OddiWire as one leg of the stack and fill the gaps from the full directory.