B2B API. Access is arranged with our team: contact@55-tech.com. For the self-serve REST API, see the v4 docs.
Quickstart
Connect, log in, and receive your first odds update.
WebSocket
Channels, filters, compression, resume and replay.
REST API
Snapshots, metadata, historical odds, CLV, and settlement.
Coverage
Sports, bookmakers, and markets, generated from the live catalogue.
What you get on every update
- Four timestamps per price. The bookmaker’s own change time, when we observed it, when we sent it, and when you received it, so you can measure the delay yourself.
- Delay published per bookmaker. Per-book bounds are on
GET /bookmakers, each marked as measured or estimated. - Stake limits.
limitis carried next to the price for close to every sharp book. See limits. - Orderbook depth.
back/layladders for exchanges and prediction markets, in one shape across venues. - A flag for stale odds.
staleOddstells you when a bookmaker cannot be refreshed. - No gaps after a disconnect. Per-channel cursors resume and replay what you missed; worst case is one REST snapshot.
- Stable IDs. A market or outcome ID means the same on every bookmaker and never changes. See core concepts.
- The whole pipeline on one key. The same
oddsIdaddresses the live price, its history and closing line, and its settlement.
Build with OddsPapi
Prediction markets & exchanges
Orderbook depth, stake limits, and native venue IDs for order routing.
Sharp-line trading & CLV
Limits, measured delay per book, staleness handling, and closing line value.
Powering a sportsbook
Schedule, markets, prices, in-play, and settlement in one pipeline.
Running a second feed
Join to an existing feed via provider IDs and the mapping endpoints.
Who runs on it
- Trading and market making: market makers, hedge funds, and syndicates running automated strategies.
- Exchanges and prediction markets: platforms sourcing realtime prices, schedules, and settlement.
- Sportsbooks and analytics: bookmakers, quant teams, and research groups.
Stay current
- Changelog: new fields, markets, and breaking changes.
- Status page: live status and incident history.
- AI / offline export: the full docs as one file for your AI tools.
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 sportsbooks, betting exchanges, and prediction markets, with orderbook depth (
back / lay ladders and liquidity) exposed in the odds channel meta field.Does OddsPapi provide bookmaker limits?
Does OddsPapi provide bookmaker limits?
Yes. The odds channel carries
limit — the maximum accepted stake — normalized across books and available for close to every sharp book. For trading and market making, size-at-price matters as much as the price itself.Can I run OddsPapi alongside another odds feed?
Can I run OddsPapi alongside another odds feed?
Yes — desks commonly run two sources for cross-validation. The fixtures channel carries provider ID mappings (
betradarId, pinnacleId, flashscoreId, opticoddsId), so joining OddsPapi to an existing feed is a lookup, not a mapping project. Coverage is complementary by design: sharp trading books, Asian lines, exchanges, and prediction markets alongside US and European retail books.Does OddsPapi support bet settlement?
Does OddsPapi support bet settlement?
Yes, for fixtures. 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. Futures settlement is rolling out — the endpoint exists but is not yet serving results.
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.
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.