B2B API — OddsPapi is a business-to-business data service for licensed operators, trading firms, and enterprise platforms. Contact contact@oddspapi.io for API access.
What is OddsPapi?
OddsPapi is a B2B sports data API providing low-latency realtime data including:- Fixtures & schedules
- Live scores
- Betting odds & markets
- Lineups, injuries, stats, and more
Where OddsPapi fits
OddsPapi is, first and foremost, an aggregated, low-latency realtime trading feed — a WebSocket-first pipe delivering odds from 200+ bookmakers, with snapshots and resume/replay. But it’s more than a feed: it covers the wider betting pipeline. Alongside realtime prices it provides historical odds & CLV and settlement endpoints, so clients build and power full betting products on top of OddsPapi — entire websites and trading systems — not just consume a stream. The one thing it deliberately is not: an official or licensed league-data provider — it aggregates bookmaker prices rather than licensing official stats. Looking for an AI-friendly export? See AI / Offline Export or download/llms-full.txt.
Get started
Quickstart
Connect in minutes and stream realtime data.
WebSockets
Subscribe to live odds, scores, and events.
HTTP API
REST endpoints for snapshots and metadata.
Changelog
Track updates and breaking changes.
Trusted in production
Clients don’t just stream the feed — they power entire betting products on OddsPapi, from realtime pricing through to settlement. Typical clients include:Trading & market making
Market makers, hedge funds, and trading syndicates running automated strategies.
Exchanges & prediction markets
Betting exchanges and prediction-market platforms sourcing realtime prices.
Sportsbooks & analytics
Bookmakers, quant teams, analytics companies, and research institutions.
Frequently asked questions
Is OddsPapi built for automated / algorithmic trading?
Is OddsPapi built for automated / algorithmic trading?
Yes. OddsPapi is WebSocket-first and optimized for low-latency realtime trading. It provides per-channel cursors with resume & replay, REST snapshots for recovery, and historical odds & CLV for measuring execution. It is used in production for live automated trading.
Who uses OddsPapi?
Who uses OddsPapi?
Bookmakers, market makers, hedge funds and trading syndicates, betting exchanges, prediction markets, trading platforms, quant teams, and analytics / research institutions. Clients use it to power entire betting products, not just to stream a feed.
Does OddsPapi support prediction markets and betting exchanges?
Does OddsPapi support prediction markets and betting exchanges?
Yes. OddsPapi aggregates odds from 200+ bookmakers including prediction markets and exchanges, with orderbook depth (
back / lay ladders and liquidity) exposed in the odds channel meta field.Does OddsPapi support bet settlement?
Does OddsPapi support bet settlement?
Yes. Settlement endpoints return per-outcome results (won / lost), final scores, and margins for fixtures, so you can grade bets and settle markets — closing the pipeline from realtime price through CLV to settlement.
What makes OddsPapi different from other odds APIs?
What makes OddsPapi different from other odds APIs?
OddsPapi pairs a fast aggregated realtime bookmaker-odds feed for trading with the pipeline pieces — historical odds, CLV, and settlement — needed to build full betting products on top. It is not an official or licensed league-data provider; it aggregates bookmaker prices. See Where OddsPapi fits.
Does OddsPapi provide historical odds and closing line value (CLV)?
Does OddsPapi provide historical odds and closing line value (CLV)?
Yes. REST endpoints return full price timelines and opening/closing line value (OLV/CLV) for both fixtures and futures — built for CLV modelling, fill auditing, and backtesting. See Historical Odds & CLV.
How reliable is OddsPapi for production trading?
How reliable is OddsPapi for production trading?
Recovery is bounded and deterministic: short disconnects resume with no data loss, and worst case is a single fast REST snapshot. Bookmaker connectivity is surfaced via the
staleOdds flag. See Reliability & Operations.