FanDuel prop results, hit rates and player data

Join each FanDuel line to what actually happened, and train on graded outcomes instead of guesses.

Graded

Closing FanDuel line, box score value, and over, under, push or void with its reason.

Matched, not guessed

Only props matched to a confirmed player and game are graded; ambiguous names stay ungraded.

Hit rates

How often the over hit across the last N games against the closing line, with the sample size.

What it returns now

Endpoints and parameters

Code

curl "https://fanduelapi.com/api/v1/players?league=NBA&q=james" \
  -H "Authorization: Bearer $FANDUEL_API_KEY"

import os, requests

r = requests.get(
    "https://fanduelapi.com/api/v1/players",
    params={"league": "NBA", "q": "james"},
    headers={"Authorization": f"Bearer {os.environ['FANDUEL_API_KEY']}"},
)
r.raise_for_status()
body = r.json()
print(body["meta"])          # plan, delay_seconds, as_of, source_status
for row in body["data"][:5]:
    print(row)

Keys look like fd_.... Keep one in the FANDUEL_API_KEY environment variable on your server, never in browser code. Every response's meta says which plan answered, how far behind it is and how fresh the collection is.

Which plans include it

• FreeIncluded, 5 minutes behind
• DeveloperIncluded, real time
• ProductionIncluded, real time
• ScaleIncluded, real time

Read from the plans on the pricing page. Every request counts against the monthly and per-minute allowance; request quotas explains how.

Works well with

• CSV and NDJSON exportsLoad a slate or a season of line history straight into pandas, DuckDB or a spreadsheet./api/v1/export
• Props feedRead the whole player prop board in one call, already normalised, with where each line opened./api/v1/props
• Line historyReplay a prop or a game line from the first time it was seen to now, move by move./api/v1/props/{id}/history