> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oddspapi.io/llms.txt
> Use this file to discover all available pages before exploring further.

# OddsPapi - B2B Sports Betting Odds API

> B2B low-latency realtime sports odds API. Stream live betting odds, fixtures, scores, lineups, injuries and statistics via WebSocket. REST API for snapshots and historical data.

<Note>
  **B2B API** — OddsPapi is a business-to-business data service for licensed operators, trading firms, and enterprise platforms. Contact [contact@oddspapi.io](mailto:contact@oddspapi.io) for API access.
</Note>

## 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

Built for **trading systems**, **sportsbooks**, **analytics**, and **media platforms**.

### 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](/api-reference/concepts#historical-odds-and-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

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Connect in minutes and stream realtime data.
  </Card>

  <Card title="WebSockets" icon="bolt" href="/websocket/overview">
    Subscribe to live odds, scores, and events.
  </Card>

  <Card title="HTTP API" icon="terminal" href="/api-reference/overview">
    REST endpoints for snapshots and metadata.
  </Card>

  <Card title="Changelog" icon="clock-rotate-left" href="/changelog/index">
    Track updates and breaking changes.
  </Card>
</Columns>

***

## 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:

<Columns cols={3}>
  <Card title="Trading & market making" icon="chart-line">
    Market makers, hedge funds, and trading syndicates running automated strategies.
  </Card>

  <Card title="Exchanges & prediction markets" icon="arrow-right-arrow-left">
    Betting exchanges and prediction-market platforms sourcing realtime prices.
  </Card>

  <Card title="Sportsbooks & analytics" icon="building-columns">
    Bookmakers, quant teams, analytics companies, and research institutions.
  </Card>
</Columns>

OddsPapi is used in production across prediction-market exchanges, hedge-fund trading desks, and top bookmakers — and is proven in live automated betting and market-making projects.

***

## Frequently asked questions

<AccordionGroup>
  <Accordion title="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](/websocket/resume-replay), REST snapshots for recovery, and [historical odds & CLV](/api-reference/concepts#historical-odds-and-clv) for measuring execution. It is used in production for live automated trading.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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](/websocket/channels/odds) `meta` field.
  </Accordion>

  <Accordion title="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](/api-reference/concepts#historical-odds-and-clv) to settlement.
  </Accordion>

  <Accordion title="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](#where-oddspapi-fits).
  </Accordion>

  <Accordion title="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](/api-reference/concepts#historical-odds-and-clv).
  </Accordion>

  <Accordion title="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](/api-reference/reliability).
  </Accordion>
</AccordionGroup>