BTCBTC$64,615-0.43%|
ETHETH$1,828.36+0.41%|
USDTUSDT$0.99936+0.00%|
BNBBNB$592.4000-0.23%|
USDCUSDC$0.99962-0.01%|
XRPXRP$0.96013+0.09%|
SOLSOL$72.8300+1.94%|
TRXTRX$0.30603+0.99%|
FIGR_HELOCFIGR_HELOC$1.0390+0.00%|
HYPEHYPE$69.7000+4.68%|
ZECZEC$924.3800+2.98%|
XMRXMR$498.0900+2.25%|
DOGEDOGE$0.05896-0.08%|
LEOLEO$9.2800+1.31%|
USDSUSDS$0.99985+0.01%|
WBTWBT$62.5700-0.38%|
LINKLINK$9.1800+0.12%|
ADAADA$0.15339-0.19%|
XLMXLM$0.13755-1.22%|
USDEUSDE$0.99938+0.00%|
DAIDAI$0.99975+0.00%|
NEARNEAR$3.2500+1.55%|
BCHBCH$208.5700+0.10%|
RAINRAIN$0.00560454-9.97%|
LTCLTC$44.6800-0.59%|
CCCC$0.08148-2.94%|
UNIUNI$5.3300+1.63%|
AVAXAVAX$7.2200+0.42%|
XAUTXAUT$3,860.2+0.40%|
SUISUI$0.72448-0.13%|
BTCBTC$64,615-0.43%|
ETHETH$1,828.36+0.41%|
USDTUSDT$0.99936+0.00%|
BNBBNB$592.4000-0.23%|
USDCUSDC$0.99962-0.01%|
XRPXRP$0.96013+0.09%|
SOLSOL$72.8300+1.94%|
TRXTRX$0.30603+0.99%|
FIGR_HELOCFIGR_HELOC$1.0390+0.00%|
HYPEHYPE$69.7000+4.68%|
ZECZEC$924.3800+2.98%|
XMRXMR$498.0900+2.25%|
DOGEDOGE$0.05896-0.08%|
LEOLEO$9.2800+1.31%|
USDSUSDS$0.99985+0.01%|
WBTWBT$62.5700-0.38%|
LINKLINK$9.1800+0.12%|
ADAADA$0.15339-0.19%|
XLMXLM$0.13755-1.22%|
USDEUSDE$0.99938+0.00%|
DAIDAI$0.99975+0.00%|
NEARNEAR$3.2500+1.55%|
BCHBCH$208.5700+0.10%|
RAINRAIN$0.00560454-9.97%|
LTCLTC$44.6800-0.59%|
CCCC$0.08148-2.94%|
UNIUNI$5.3300+1.63%|
AVAXAVAX$7.2200+0.42%|
XAUTXAUT$3,860.2+0.40%|
SUISUI$0.72448-0.13%|
OddsPapi
Tool / APITier-1Odds APIVerified

OddsPapi

One API that puts Polymarket, Kalshi and Prophet Exchange beside 350+ sportsbooks in decimal odds — the benchmark price for judging whether a prediction market quote is signal or noise.

Visit website

Key Facts

CategoryOdds API
AccessFree tier with an API key, and historical odds are free to backtest on. Paid access is built from a configurator rather than fixed tiers: you choose the bookmakers and sports you want, set a request volume, and the monthly price is calculated from those — with a trial available to check coverage before buying. Documentation warns coverage is a goal rather than a guarantee, so a free account is the recommended way to verify a specific book first. The API is strictly read-only: it aggregates and normalises data, and places no orders.
Venues CoveredPrediction markets and exchanges: Polymarket, Kalshi, Prophet Exchange, Betfair Exchange, Matchbook, 4casters. Sportsbooks: 350+ including Pinnacle, bet365, DraftKings, FanDuel, BetMGM, Caesars and Stake.
Data ConfidenceVerified
Last Reviewed1 Oct 2026

What It Does

A sports betting odds API that treats prediction markets as first-class bookmakers, so Polymarket, Kalshi and Prophet Exchange sit in the same response as Pinnacle, bet365 and DraftKings, every price already normalised to decimal odds and every market carrying consistent IDs. Its argument to prediction market users is not more market data but a reference point: prediction markets run thinner liquidity and lower limits than major sportsbooks, so a Polymarket quote on its own is hard to judge — put it beside a sharp book and you can start separating signal from noise, comparing the price, the lay side and the order-book depth that prediction markets expose under exchangeMeta. Coverage is deliberately deep rather than total: live odds from 250+ of its 350+ books across 60+ sports, ten sharp books for the reference prices that matter, plus pre-match, live, futures, handicaps, totals and player props, with historical odds free so a strategy can be backtested before it is traded. Delivery is REST for pulls and a low-latency WebSocket push feed for line movement. Two limits are worth knowing before planning around it: prediction market coverage on Kalshi is limited to sports markets where its coverage overlaps — NFL and NBA rather than elections, economics or weather, which still need Kalshi's own API — and the product is read-only, aggregating and normalising data without ever placing an order.

Overview

What it is

OddsPapi is a sports betting odds API that treats prediction markets as first-class bookmakers. Polymarket and Kalshi sit in the same response as Pinnacle, bet365, DraftKings and FanDuel, as native bookmaker slugs, with every price already normalised to decimal odds and every market carrying the same identifiers across books. Delivery is a REST API plus a low-latency WebSocket feed for line movement.

Its relevance in a prediction-market directory is not more market data — it is a reference point. That argument is the vendor's own, and it is a good one.

Why a prediction-market reader cares

A Polymarket or Kalshi quote on its own is hard to judge. Prediction markets run thinner liquidity and lower limits than major sportsbooks, so a wide price can mean an edge or simply mean nobody is quoting size. Put the same event next to a sharp book and you can start separating the two: compare the price, use the lay side and order-book depth that prediction markets expose under exchangeMeta, and check the stake limits returned with each outcome. This is the benchmark layer that the rest of this directory's venue pages cannot give you on their own.

What the coverage actually looks like

The vendor's marketing says 350+ bookmakers across 60+ sports, and its own May 2026 comparison post measured 370 bookmakers live from the /v4/bookmakers endpoint, visible to any key including the free tier. The catalogue breaks down into three groups worth knowing: sharp books for reference pricing (Pinnacle among them), exchanges including Betfair Exchange, Matchbook and an Asian exchange network (4casters, Fair999, Orbit, Piwi247 and Sharp Exchange), and crypto books such as 1xBet, Stake, BC.Game, Rollbit and Cloudbet. Prediction markets are a small, separate category on top.

Unusually, the site documents its own latency in detail — maximum live delay and pre-game delay per bookmaker, measured from the moment a price changes to the moment it reaches the WebSocket feed, with the polling-versus-push distinction spelled out for each. On the review date the coverage table on that page rendered no rows at all, so the metric, the method and the vendor's own observation that slower web-based books hover around 4–10 seconds are readable, but a current per-book figure is not.

The Kalshi caveat

This is the most important limitation for prediction-market users, and it is stated in the vendor's own developer guide rather than hidden: Kalshi appears as a bookmaker with live odds, but only for sports markets where coverage overlaps — the guide names NFL and NBA. Kalshi-only categories such as elections, economic indicators and weather are not covered and still need Kalshi's own API. Polymarket coverage is broader and includes the lay side, but the practical consequence is that OddsPapi is a bridge between prediction markets and sportsbooks, not a replacement for either venue's API.

Read-only by design

Every endpoint in the documentation is a read. OddsPapi aggregates, normalises and streams data; it does not place, modify or cancel orders, and it holds no funds. Execution stays at the venue, which means position sizing, fees, spreads and settlement risk remain yours to manage — the API only tells you what is being quoted.

Where it sits in this directory

Three layers are useful to keep apart. Venue APIs and pages tell you what a specific market is pricing. Dune gives you the authoritative historical record with SQL. OddsPapi sits between them as the cross-venue price feed: it answers what the same event is trading at elsewhere, including at books whose pricing is generally more efficient than a thin prediction market's. Alphascope-style research workspaces interpret; OddsPapi supplies.

Counters you should not quote

The site's bookmaker count still depends on which page you read, which is why none of the figures should be repeated as a fact: the documentation intro says 300+ bookmakers across 60+ sports, the pricing and bookmaker pages say 350+, the Polymarket bookmaker page repeats 350+, a US-locale hero recorded earlier in September read 125+ across 21+ sports, and the vendor's own May 2026 blog post measured 370 from the /v4/bookmakers endpoint. The difference is plausibly regional filtering of the catalogue, but the pages do not label the figures that way. The vendor's own recommendation is the right one: take a free key and call the bookmakers endpoint to check the books you actually need before paying for anything.

How It Works

Getting a key and making the first call

Signing up produces an API key, and the documentation's onboarding path is three steps: fetch leagues for a sport, fetch upcoming events by tournament, then request odds for those events from a chosen bookmaker. Requests go to https://api.oddspapi.io with the key passed as the apiKey parameter, and responses are JSON. The /v4/bookmakers endpoint returns the catalogue, which is the sane first call — it tells you whether the specific books you care about are actually there before you plan around them.

The shape of an odds response

Each fixture carries its own identifiers and timing (fixture id, participants, sport, tournament, season, status, start time, an updatedAt stamp and a hasOdds flag), and then a bookmaker block keyed by slug. Inside each bookmaker are markets, inside those outcomes, and inside those players. The leaf fields are where the useful detail lives:

  • price — the decimal odds actually offered.
  • limit — the maximum stake allowed on that price, which is the fastest way to see whether a quote is real.
  • active and changedAt — whether the price is still live and when it last moved.
  • exchangeMeta — exchange metadata, including the back and lay side for prediction markets and exchanges.
  • bookmakerMarketId and fixturePath — the book's own identifiers and a deep link to the market.

Stable IDs across books are the quiet value: because the same market and outcome IDs are used for every bookmaker, you can compare Pinnacle, Polymarket and Kalshi on one event without mapping anything yourself.

Pulling prediction markets and sportsbooks together

Because Polymarket and Kalshi are addressed as bookmaker slugs, the comparison is a single parameter. A request for one fixture with bookmakers=polymarket,kalshi,pinnacle returns all three in one response, already normalised, which is the query this API exists for: the prediction market price, the second prediction market price, and the sharp reference, side by side. Filtering by sport or tournament keeps the volume manageable.

Historical odds and backtesting

The historical endpoint returns a per-outcome history for a fixture: each entry carries a timestamp, the price, the stake limit, whether it was active, and any exchange metadata, so you can reconstruct how a line moved rather than just where it ended. Four practical details shape how you build against it:

  • Depth: the documentation states that all historical odds data since January 2026 is available — this is a recent window, not a multi-year archive.
  • Bookmakers per query: a historical request takes a maximum of three bookmaker slugs at a time.
  • Conditional requests: for finished or cancelled events the response is deterministic and returns an ETag, so polling clients can send If-None-Match and receive a 304 with an empty body instead of re-downloading unchanged history. The cache window is private and three days.
  • Rate limit: the historical endpoint has a five-second cooldown, and a 304 response still counts against it.

A settlements endpoint sits alongside the odds endpoints, which is what you need to close the loop — prices tell you what was offered, settlements tell you what the market resolved to.

Live streaming

For live line movement there is a WebSocket feed rather than polling. It sits on a paid plan: the free tier is explicitly pre-game REST, with live odds, player props and deeplinks on the custom plan and streaming above it — and the vendor's own pages do not agree on what that higher plan is called, since its comparison post calls it Pro while its plan pages have used B2B, so confirm the name when you upgrade. Polymarket's bookmaker page lists WebSocket as available for live odds, so prediction-market prices can be streamed alongside the sportsbooks.

How the plans work

PlanWhat it includes
FreePre-game REST API, unlimited sports and bookmakers, historical data, 250 requests per month
CustomConfigurator pricing: choose the bookmakers and sports you want, set a request volume, get a monthly price. Adds live odds, player props and deeplinks
B2BReal-time odds via WebSocket, dedicated support, vendor-built bookmaker additions on request

Billing is per request rather than credit-weighted — the vendor's own comparison makes a point of one request equalling one request whether it is live odds or two-year-old history. A trial exists to check coverage before buying.

A practical recipe for prediction-market work

Call the bookmakers endpoint on a free key and confirm Polymarket, Kalshi and your sharp reference are all present. Pull one fixture with those three slugs together and compare the implied probability from the prediction markets against the book consensus — a divergence is the thing worth investigating. Check the limit on each prediction-market outcome before treating a gap as tradeable, and read the lay side from exchangeMeta rather than assuming the mid. Backtest against the historical endpoint knowing the window starts in January 2026, then pair odds history with settlements so results are measured on what actually resolved.

Method Notes & Limitations

Where this review's facts come from

Everything here was read from OddsPapi's own material on the review date, 30 September 2026: the homepage, the API documentation and the historical odds endpoint reference, the Polymarket bookmaker page, the coverage and latency page, and the vendor's own blog posts on prediction-market APIs and odds API comparisons. No API key was created, no request was made against the API, and no coverage claim was independently tested. Claims that come only from vendor marketing are labelled as such throughout.

Verified against vendor claims

ClaimStatus
Polymarket is supported as a bookmaker slug with live odds and WebSocket availabilityVerified — stated on the Polymarket bookmaker page and in the developer guide
Kalshi is supported only for sports markets where coverage overlaps (NFL, NBA), not elections or economic indicatorsVerified — stated in the vendor's own developer guide FAQ
Endpoints, host, authentication and response shapeVerified — taken directly from the API documentation
Historical odds availability since January 2026, three bookmakers per query, five-second cooldown, ETag conditional requestsVerified — documented on the historical odds endpoint reference
Plan structure and the 250 requests per month free tierVerified — shown on the pricing section and repeated on the bookmaker pages
350+ bookmakers, 60+ sports, 300+ bookmakers, 21+ sports, 370 bookmakersVendor claims; the figures conflict across the site — see below
Unified coverage of prediction markets and sportsbooks in one queryClaim supported by documented slugs and response structure, but not tested by Bitnxt

The bookmaker count does not hold still

The same vendor publishes several different totals, and buyers should notice before quoting any of them: 300+ bookmakers and 60+ sports on the global homepage, 125+ bookmakers and 21+ sports on the US locale, 350+ on the pricing and bookmaker pages, and 370 in its own May 2026 blog post. The most likely explanation is that locale paths return a region-filtered catalogue, but nothing on the page says that, and the free tier exposes the same bookmakers endpoint the blog used to count them. If the number matters to your decision, count it yourself on a key.

Coverage guarantees, in the vendor's words

OddsPapi states plainly that the goal is to cover all odds on bookmaker sites but that this is not guaranteed, and it recommends taking a free account to check the books you care about before purchasing. That is unusually candid and it should be taken literally: treat the catalogue as a goal and verify the specific books and markets you need before building on them. The latency page deserves the same treatment — it documents exactly how delay is measured and what it means for a polling client versus a push client, but on the review date its coverage table returned no rows, so the method is published while current per-book figures are not. The top plan exists partly for coverage gaps, since the vendor will add bookmakers on request.

History depth and practical limits

Two constraints will shape any backtest. Historical odds reach back to January 2026, so strategies cannot be validated on older regimes — a meaningful limitation compared with the deeper archives available from other data sources in this directory. And each historical query takes at most three bookmakers, with a five-second cooldown on the endpoint, so wide multi-book reconstructions need to be batched and paced. The ETag support softens this for finished events, since unchanged history can be re-fetched for free in bandwidth terms, though not in rate-limit terms. Billing is per request without credit weightings, which makes cost predictable once you know your polling pattern.

Read-only, and what that implies

Every endpoint in the documented surface is a read, and the API takes no orders and holds no funds. That is the right design for a data provider, but it means the numbers it returns are only inputs: limits, fees, spreads, settlement rules and account access at each venue still govern whether a quoted edge can be captured. Note also that deep links are a paid feature, which is a normal monetisation route for an API that supplies odds-comparison and affiliate products — the price feed is the product, and the paid tier exists to help build the funnel around it.

Editorial note

Bitnxt is not affiliated with OddsPapi and has no commercial relationship with it; this page carries no referral arrangement and no trading or betting links. OddsPapi is a data provider, not a venue, and nothing here is investment or betting advice. Coverage changes as bookmakers are added or dropped and as feed delays shift, so re-check the bookmakers and latency pages before building a strategy that depends on either.

Venues Covered

Prediction markets and exchanges: Polymarket, Kalshi, Prophet Exchange, Betfair Exchange, Matchbook, 4casters. Sportsbooks: 350+ including Pinnacle, bet365, DraftKings, FanDuel, BetMGM, Caesars and Stake.

Access & Pricing

Free tier with an API key, and historical odds are free to backtest on. Paid access is built from a configurator rather than fixed tiers: you choose the bookmakers and sports you want, set a request volume, and the monthly price is calculated from those — with a trial available to check coverage before buying. Documentation warns coverage is a goal rather than a guarantee, so a free account is the recommended way to verify a specific book first. The API is strictly read-only: it aggregates and normalises data, and places no orders.

Frequently Asked Questions

Sources & Verification

The factual claims on this page were checked against the sources below.

Bitnxt uses cookies to run the site, understand how it is used, and measure ads. You can accept or decline below, and change your choice any time in our Privacy Policy.