Caesars Odds API

Caesars is the fourth name in the standard US book set, and it behaves like it. It is listed in every full game lines category we publish — NFL, NBA, MLB, NHL and the Premier League — and in the headline prop rows alongside DraftKings, FanDuel and BetMGM.

Where it steps back is the second layer down, and that is a more useful thing to know than another paragraph about how many sports it covers.

Strong at the top, selective below

Caesars is absent from several of the secondary stat categories we list: MLB pitching props, NBA defensive props (blocks, steals, turnovers), NHL physical and two-way props (hits, blocks, faceoffs won), and both of the Premier League categories covering shots and passing.

The pattern is consistent enough to plan around. If a market is one a casual bettor would recognise — moneyline, spread, total, points, touchdowns, goals, quarter and half lines — Caesars is very likely pricing it. If it is a stat split that mostly interests modellers, it is worth checking rather than assuming.

That makes it a reliable member of the comparison set and a poor sole source for anything prop-heavy or stat-driven. The /markets endpoint returns the supported set by league from live data, which is the authoritative version.

Which plan includes Caesars

Caesars is on the free Amateur tier, alongside DraftKings, FanDuel, BetMGM, ESPN BET, Bovada, Unibet, PointsBet and William Hill. 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 Caesars prices

Filter to Caesars alone with bookmakerID=caesars:

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

More usefully, request the standard US set in one call:

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

All four of those books are on the free tier, so that request runs on a free key.

What a Caesars price looks like

{
  "eventID": "...",
  "leagueID": "NFL",
  "odds": {
    "points-all-game-ou-over": {
      "oddID": "points-all-game-ou-over",
      "opposingOddID": "points-all-game-ou-under",
      "marketName": "Total Points Over/Under",
      "statID": "points",
      "statEntityID": "all",
      "periodID": "game",
      "betTypeID": "ou",
      "sideID": "over",
      "fairOdds": "-104",
      "fairOverUnder": "44.5",
      "bookOdds": "-110",
      "byBookmaker": {
        "caesars": { "odds": "-108", "overUnder": "44.5", "available": true },
        "draftkings": { "odds": "-110", "overUnder": "44.5", "available": true }
      }
    }
  }
}

Game totals use all as the statEntityID rather than a team or player ID, and points is the score stat for every sport — goals, runs and points all arrive under the same statID, which is what lets one piece of parsing code handle every league.

Odds and lines are both strings, so -108 stays "-108" and "44.5" does not quietly become a float.

Coverage, honestly

Caesars does not price every market, 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.

Anything you hardcode from a coverage 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 Caesars data

Odds comparison is the direct one. Users expect to see Caesars next to DraftKings, FanDuel, BetMGM and ESPN BET, and a grid that omits it looks incomplete regardless of whether its price is best.

For arbitrage and positive EV work, measure it against the vig-free fairOdds consensus rather than against any single rival book — even a sharp one like Pinnacle.

For live and in-play products, the quarter, half and period markets are carried pre-match and live.

Caesars API technical specifications

Caesars 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, so a ten-game slate is ten objects whether you ask for Caesars alone or Caesars alongside eighty others. Adding books to a request you were already making costs response size and nothing else.

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.