OddsPapi API Review 2026

OddsPapi is a real-time sports odds API built for developers, arbitrageurs, and quants shipping models that need to read the market. Instead of scraping and reconciling dozens of sportsbook sites, you pull odds from 350+ bookmakers through one consistent JSON REST API, with a WebSocket feed on top for push updates. A free tier lets you wire it into a project and see real data before you spend anything.

The combination is the draw. Plenty of odds APIs cover the obvious US books. Far fewer put sharp books, exchanges, and prediction markets in the same normalized feed, and fewer still include historical odds at no extra charge. If you have ever stitched together three providers to get sharp prices, soft books, and backtest data, OddsPapi wants to be the one feed that replaces that stack.

Coverage is where OddsPapi earns its place. The breadth spans market segments that usually require separate, specialized providers:

• 350+ bookmakers in one feed. A single normalized schema across the whole set, so you write one parser instead of one per book.
• Sharp books: Pinnacle, SBOBET, and Singbet (Crown), the low-margin, high-limit books whose lines move the market and serve as a fair-value reference.
• Soft / US books: Bet365, DraftKings, FanDuel, and BetMGM, the recreational books where the soft prices (and the edges) live.
• Crypto / niche: 1xBet, Stake, and BC.Game. Most mainstream odds APIs skip these entirely.
• Exchanges & prediction markets: Betfair Exchange, Polymarket, and Kalshi, putting exchange prices and event-contract markets alongside traditional books.
• 69 sports: soccer, basketball (the NBA and NCAA basketball), tennis, baseball, the NFL and college football (NCAAF), NHL, MMA, cricket, esports, and more.

The practical upshot: if your strategy compares a sharp anchor (say, Pinnacle) against a soft book (say, DraftKings), one request covers it. That job used to take two vendors with two schemas and two rate limits.

• Free historical odds for backtesting. Historical pricing is included rather than locked behind an enterprise add-on. If you test models against real closing lines and movement, that alone is a meaningful cost difference. Many competitors charge for historical odds.
• Real-time WebSocket push feed. You subscribe and receive updates as the market moves instead of hammering a REST endpoint on a timer. For live betting and market-making, WebSocket push is the difference between reacting in milliseconds and reacting on your poll interval.
• Native support for complex markets. Asian handicaps, player props, and totals are first-class. That matters if your edge lives in derivative or props markets rather than moneylines.
• Parlay, same-game parlay, and futures odds. Dedicated endpoints price accumulators and correlated same-game parlays from the oddsIds you pick, with bookmakers side by side and the correlation margin exposed. Futures and outright markets (league winners, season-long markets) get their own endpoints and WebSocket channel, with historical odds and closing line value (CLV).
• Official MCP server for AI agents. A hosted MCP server at https://docs.oddspapi.io/mcp connects Claude, Cursor, and other agents to the full docs and OpenAPI spec, so your agent writes working OddsPapi calls without you pasting docs into the chat. Nothing to install.
• Clean JSON REST API. Predictable JSON, simple query-parameter auth, no SDK lock-in. You can pull odds with a single requests.get call.
• Free tier to start. Get a key, hit the API, and validate the data against your own use case before paying. The free plan covers pre-game REST odds and historical data at 250 requests a month. In-play odds and the WebSocket need a paid plan.

Authentication is a query parameter (apiKey), not a header. Note that up front so your first request does not 401. Here is a minimal Python example that lists available sports:

import requests
API_KEY = "YOUR_API_KEY"
BASE_URL = "https://api.oddspapi.io/v4"
# Auth is a query parameter (apiKey), NOT a header
resp = requests.get(f"{BASE_URL}/sports", params={"apiKey": API_KEY})
print(resp.json())

From there you swap /sports for the odds endpoints, pass the bookmakers and markets you care about, and either poll the REST API or subscribe to the WebSocket feed for live updates. Full docs and a key are on oddspapi.io.

The breadth-plus-history combination maps cleanly onto a few developer workloads:

• Arbitrage bots surfacing two-way and multi-way arbitrage across 350+ books, including exchanges, where mispricings actually appear.
• Value-betting / +EV scanners comparing soft-book prices against a sharp anchor to flag positive expected value.
• Line-shopping tools showing users the best available price per market across every book in the feed.
• Trading and market-making models consuming the WebSocket feed to react to line moves as they happen.
• Odds-comparison sites powering a public comparison product from one normalized source.
• Model backtesting validating strategies against the free historical odds before risking capital.

The odds API market splits into two extremes. On one end sit enterprise data feeds: complete, including sharps and exchanges, but priced for funded operations and gated behind sales calls and contracts. On the other end sit thin, generic APIs that are cheap and easy to start with but only cover around 40 mainstream books, sell historical data as a paid extra, and skip exchange and sharp coverage.

OddsPapi positions itself between the two: enterprise-grade coverage (sharp books, exchanges, crypto books, complex markets) at a developer-friendly price, with a genuine free tier and free historical odds. If the cheap generic APIs leave gaps in your coverage and the enterprise feeds are overkill for your budget, that middle is the slot the OddsPapi sports odds API aims for. Validate the specific books and markets you depend on against your own requirements before you commit.

OddsPapi prices its self-serve plan by what you pick, so its pricing page has a plan builder instead of a fixed price list (checked November 2026).

• Free: pre-game REST odds, every sport and bookmaker, historical data and 250 requests a month.
• Custom Plan: live odds, player props and deeplinks, built in three steps. First the bookmakers. Each book has its own base price, shown once you sign in. Live odds double a book's price and player props add 50%, while 10, 20 or 30 books take 10%, 15% or 20% off. Then the sports: $5 each for the Big 6 (10% off all six), $3 per esport, $2 for any other. Last, a request tier multiplies the total: Normal ×1 (about 5,000 requests a month), Dev ×2 (100,000), Pro ×5 (500,000) or Ultra ×10 (1.5 million).
• B2B: arranged with OddsPapi directly, for the v5 WebSocket feed and dedicated support.

Cancel any time from the dashboard. Open a free account at OddsPapi, then price your book list.

Sign up on the OddsPapi sign-up page with an email and a password. The form asks for no card. OddsPapi emails you a confirmation code, and once you enter it, the key waits in your account settings. A Refresh API Key button sits next to it; pressing it kills the old key on the spot, so swap the new one in right away. The new account starts on the Free plan, and its monthly quota resets on the 1st (checked November 2026).

That key belongs to the self-serve REST API, v4 at https://api.oddspapi.io/v4, and it travels as the apiKey query parameter on every call. The B2B plan runs on v5 at https://v5.oddspapi.io/en with its own key, which also works in an X-API-Key header. The site lists no fixed trial length. Trial access to v5 goes through contact@55-tech.com.

The quick start above lists sports. The next step in the v4 docs lists the leagues inside one sport: GET /v4/tournaments with a sportId, where 10 is soccer. Same free key, same query parameter. This sample comes from the docs, checked November 2026.

import os

import requests

resp = requests.get(
    "https://api.oddspapi.io/v4/tournaments",
    params={"sportId": 10, "apiKey": os.environ["ODDSPAPI_API_KEY"]},
    timeout=10,
)
resp.raise_for_status()

for t in resp.json()[:10]:
    print(t["tournamentId"], t["tournamentName"], t["upcomingFixtures"])

Each row carries a tournamentId (17 is the Premier League), a tournamentName and three counts: upcomingFixtures for games inside 24 hours, futureFixtures for later ones and liveFixtures for games in play. Pass a few of those IDs to /v4/odds-by-tournaments with a bookmaker and you're reading prices. The call costs 1 request, and the docs put a 1 second cooldown on it.

On v4 the limit is a cooldown per endpoint, per key. Wait 0.5 seconds between calls to /v4/odds or /v4/fixture, 1 second on lookups such as sports, bookmakers, tournaments and /v4/odds-by-tournaments, 2 seconds on /v4/fixtures and settlements, and 5 seconds on historical odds and players. Call too soon and you get a 429 with the code RATE_LIMITED and a retryMs wait. A spent monthly quota is a 429 too, coded REQUEST_LIMIT_EXCEEDED, so branch on the code. /v4/account never counts against the quota, and historical odds calls don't either.

v5 allows 10 requests a second on the odds endpoints and 100 a minute elsewhere, sends X-RateLimit-* headers and caps a key group at 5 WebSocket connections (checked November 2026). There's no official SDK, but the v5 docs publish an OpenAPI spec at /api-reference/openapi.json, a changelog and a status page at oddspapi-v5.instatus.com. The v4 docs live on oddspapi.io. For help, write to contact@55-tech.com or ask in the OddsPapi Discord.

OddsPapi fits developers and high-volume bettors who need broad bookmaker coverage, sharp prices, and historical data without an enterprise contract. Building an arbitrage bot, a value-betting scanner, a line-shopping tool, or a trading model that wants sharps, soft books, and exchanges in one feed with backtest data included? Wire up the free tier and point it at your own use case.

It is less essential if you only need a handful of US books and never touch historical data; a thinner generic API may be enough there. For anyone whose edge depends on where and how broadly they can read the market, the coverage and the included history are the differentiators. Grab a key and test it against your strategy.

What stood out when we vetted OddsPapi for the directory:

• Excellent coverage of sportsbooks in the EU/US
• Websocket and realtime odds
• Extensive documentation and example code

EU based provider with 300+ bookmakers and extensive sport and market coverage. Also offers rare books including prediction markets and crypto sportsbooks.

Last reviewed: 2 November 2026 · How providers get listed