Fanatics Odds API

Look at where Fanatics turns up in our own coverage tables and a pattern shows up quickly. It is not in the rows for moneylines and spreads, where almost every book appears and the numbers mostly agree. It is in the prop rows.

That is the case for carrying it, and it is a narrower case than "one more book on the list."

Where Fanatics actually shows up

Across the league pages, Fanatics sits in the player prop rows more consistently than the game line rows:

• NFL — passing props (passing_yards, passing_touchdowns, passing_completions) and rushing and receiving props (rushing_yards, receiving_yards, receiving_receptions)
• MLB — batting props (batting_hits, batting_homeRuns, batting_totalBases) and pitching props (pitching_strikeouts)
• Soccer — card markets, including yellowCards, redCards and combinedCards
• NHL — the core game lines alongside the other major US books

Game lines and props are not the same problem. A spread on a major NFL game is priced by dozens of books watching each other, and the numbers cluster. A prop on a third receiver is priced with less liquidity and more room for a book's own view, so the spread between the best and worst available number is wider — and which books you happen to carry matters more.

That is the argument for a prop-heavy book specifically. On a spread, the marginal book changes your best price by a cent or two. On a prop, it can change it by a lot more.

Which plan includes Fanatics

Fanatics is available on the Pro plan and above, in the same group as Bet365, Circa, Pinnacle and PrizePicks. Neither the free Amateur tier nor the Rookie plan carries it, so a request filtered to fanatics on those plans returns an empty result rather than an error. Pricing lists the books on each tier.

Worth knowing if you are building prop tools: PrizePicks is gated the same way. A product whose whole premise is comparing prop lines is a Pro-tier product, not a Rookie one.

Requesting Fanatics prices

Filter to Fanatics alone with bookmakerID=fanatics:

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

For prop comparison you want several books on the same market, which is the same request with a longer list:

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

Props come back in the same /v2/events response as the game lines. There is no separate props endpoint to call and reconcile.

What a Fanatics prop looks like

Player props use the player's ID as the statEntityID, so the oddID follows the same {statID}-{statEntityID}-{periodID}-{betTypeID}-{sideID} pattern as everything else:

{
  "eventID": "...",
  "leagueID": "NFL",
  "odds": {
    "passing_yards-JALEN_HURTS_1_NFL-game-ou-over": {
      "oddID": "passing_yards-JALEN_HURTS_1_NFL-game-ou-over",
      "marketName": "Jalen Hurts Passing Yards Over/Under",
      "statID": "passing_yards",
      "statEntityID": "JALEN_HURTS_1_NFL",
      "periodID": "game",
      "betTypeID": "ou",
      "sideID": "over",
      "fairOdds": "-108",
      "fairOverUnder": "224.5",
      "bookOdds": "-112",
      "byBookmaker": {
        "fanatics": { "odds": "-105", "overUnder": "223.5", "available": true },
        "draftkings": { "odds": "-115", "overUnder": "224.5", "available": true }
      }
    }
  }
}

Two things that matter here. Odds and lines are both strings, so -105 arrives as "-105" and "223.5" stays a string rather than becoming a float you have to guard against. And the two books are not on the same number — Fanatics is at 223.5 and DraftKings at 224.5. On props that happens constantly, and handling a line difference rather than only a price difference is most of the work in a prop comparison tool.

fairOdds and fairOverUnder give you the vig-free consensus across every book pricing that market, so you have a reference without building one.

Coverage, honestly

Fanatics does not price every prop, 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. The /markets endpoint returns the supported set by league if you would rather check before requesting odds than handle it at runtime.

Prop catalogues also change more than game lines do. Books add and drop prop types between seasons and sometimes within them, so anything you hardcode is a bug waiting for a quiet week.

Coverage is also uneven by sport rather than uniformly deep. Fanatics is strongest on the US prop categories; the soccer attacking props are named to a different set of books again, which the BetOnline Odds API page covers.

Use cases for Fanatics data

Prop comparison is the direct one. Wider spreads between books mean more to find, and the finding only works if the lines as well as the prices line up on a shared oddID. See the odds comparison API.

For positive EV work, props are usually where the edge is, precisely because they are priced with less scrutiny than a marquee spread. A book with deep prop coverage gives your model more markets to disagree with.

Player prop tooling more broadly benefits from carrying books that price the long tail rather than only the headline markets, and DFS-style products can put a sportsbook prop line next to a fantasy projection on the same player and stat. Our provider guide compares what the main prop data sources actually return.

Fanatics API technical specifications

Fanatics comes through the standard /v2/events endpoint, with no separate call, credential or schema.

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. Props are the clearest case where that matters: a single football game can return hundreds of prop markets and still counts once.

Odds refresh sub-minute on Pro. The API documentation covers authentication, pagination and the full parameter list, and handling odds covers reading byBookmaker in code.