DraftKings Odds API

Most US-facing products treat DraftKings as the number to beat. It is the price users expect to see, the one product screenshots default to, and the one your comparison grid looks wrong without.

That makes it the useful baseline rather than the interesting outlier. The question worth answering on a page like this is not whether to carry it — you will — but where it stops.

Where DraftKings stops

It is listed in nearly every market category we publish across the NFL, NBA, MLB, NHL and Premier League coverage tables, including the deep rows: quarter and half splits, individual innings in baseball, shooting and defensive props, corner and card markets.

The gaps are narrow and they cluster in one place. DraftKings is absent from two Premier League categories — shots and attacking props (shots, shots_onGoal, shots_assisted, dribbles_attempted, assists) and passing and defensive props (passes attempted, tackles, clearances, fouls). Those rows list a different set of books entirely, including BetOnline and the DFS operators.

That is a useful signal if you are building soccer coverage: the major US books run deep on US sports and thin out on soccer's granular player props. Carrying DraftKings does not get you those markets, and no amount of more US books will either.

The /markets endpoint returns the supported set by league from live data, which is the authoritative version.

Which plan includes DraftKings

DraftKings is on the free Amateur tier, alongside FanDuel, BetMGM, Caesars, ESPN BET, Bovada, Unibet, PointsBet and William Hill. You can build a working price comparison against real DraftKings data without paying anything.

The free tier limits the league list, the request rate and the refresh interval rather than the book's markets. Pricing has the detail.

Requesting DraftKings prices

Filter to DraftKings alone with bookmakerID=draftkings:

curl "https://api.sportsgameodds.com/v2/events?leagueID=NFL&bookmakerID=draftkings&oddsAvailable=true" \
  -H "x-api-key: YOUR_API_KEY"

More usefully, request it as the reference against the books you are checking it with:

curl "https://api.sportsgameodds.com/v2/events?leagueID=NFL&bookmakerID=draftkings,fanduel,betmgm,pinnacle&oddsAvailable=true" \
  -H "x-api-key: YOUR_API_KEY"

Every book in the response sits under the same oddID, so comparing them is a lookup rather than a name-matching exercise.

What a DraftKings price looks like

{
  "eventID": "...",
  "leagueID": "NFL",
  "odds": {
    "points-home-game-sp-home": {
      "oddID": "points-home-game-sp-home",
      "opposingOddID": "points-away-game-sp-away",
      "marketName": "Spread",
      "statID": "points",
      "statEntityID": "home",
      "periodID": "game",
      "betTypeID": "sp",
      "sideID": "home",
      "fairOdds": "-106",
      "fairSpread": "-3.5",
      "bookOdds": "-110",
      "bookSpread": "-3.5",
      "byBookmaker": {
        "draftkings": { "odds": "-110", "spread": "-3.5", "available": true },
        "fanduel": { "odds": "-115", "spread": "-3.5", "available": true },
        "pinnacle": { "odds": "-104", "spread": "-3", "available": true }
      }
    }
  }
}

Two things worth reading carefully. Spread markets carry their line in fairSpread and bookSpread, and per book in spread — not in the overUnder fields, which totals use. And Pinnacle is on -3 while DraftKings and FanDuel are on -3.5: books disagree on the line, not only the price, so a comparison that reads odds without reading spread will produce nonsense.

Values are strings throughout, which keeps the leading + intact on plus-money prices and away handicaps.

Coverage, honestly

DraftKings does not price every market in every league, and no single book does. Read byBookmaker on each odd rather than assuming it is there, and treat its absence as normal rather than as an error.

Coverage shifts as markets open and close, so anything you hardcode from a table — ours included — is a bug waiting for a quiet week. Query /markets if you would rather check up front than handle it at runtime. Every book we carry, and the plan each one is on, is listed on the bookmakers index.

Use cases for DraftKings data

Odds comparison is the direct one, and DraftKings is usually the anchor column rather than one of the alternatives.

For arbitrage and positive EV work, measure it against the vig-free fairOdds consensus rather than against any single rival book. A two-book comparison tells you which of two books is better; it does not tell you whether either is good.

For player prop tools, DraftKings is a solid US anchor but not a complete picture — pair it with the DFS operators and prop specialists for the categories it does not post.

DraftKings API technical specifications

DraftKings comes through the standard /v2/events endpoint, with no separate call, credential or schema for any individual book.

Billing is per event object rather than per market or per book. A ten-game NFL Sunday is ten objects whether the response carries four books or eighty, and whether it carries four markets per game or four hundred.

Odds refresh sub-minute on Pro, with a longer interval on Rookie and the free Amateur tier. Scores and settlement data ship alongside the odds, so there is no separate results integration — see bet tracking and settlement. The API documentation covers authentication, pagination and the full parameter list, handling odds covers reading byBookmaker in code, and there are SDKs for TypeScript, Python, Ruby, Go and Java.