draftkings apiDashboard ↗

WHO THIS IS FOR

DraftKings DFS salary API: slates, contests and roster-slot salaries

For developers building DFS tools on current DraftKings slates and roster-slot salaries. Not for contest results, ownership, salary history or republishing rows.

Editorial review: · Not a live coverage report

Who this is for

Developers building lineup tools, salary explorers and research scripts on DraftKings daily fantasy data: sports, contests, slates and draftables, for the slates we collected. Operated by DD Inc., an independent service not affiliated with or endorsed by DraftKings.

  • Lineup and slate tools that need salary per roster slot, not per athlete.
  • A project that wants DFS salaries and Pick6 rows behind one key.
  • Internal analysis where capture evidence matters: every row keeps its source URL, payload hash and capture clock.

Not for

DFS data splits into several jobs. This API covers one of them, and DFS access is a beta with a permission boundary.

  • Contest results, winning lineups and actual ownership. Not supplied. STAT-API claims these source.
  • Years of historical salaries. Not supplied. Recording here is new, and STAT-API claims salaries since 2016 source.
  • Every slate. Collection is selected draft groups, not all available slates, and no refresh schedule is guaranteed.
  • Republishing salaries. DFS redistribution is pending source permission, and rows state a rights_status.
  • FanDuel, Yahoo or other operators. This API has DraftKings only.
  • Push delivery. DFS rows have no stream or webhooks.
  • Treating a salary as a price. A salary is a lineup budget value, not a line or odds.

Try it without a key

/api/v1/demo/pick6 and /api/v1/demo/dfs need no key and spend no quota. They return invented rows labeled sample: true in the real response shape, from a static fixture. The sample shows one athlete in two roster slots, because that is the case most integrations get wrong.

No key needed
curl --fail-with-body "https://draftkingsapi.com/api/v1/demo/dfs"
With a free key: find the slate, then read salaries
curl --fail-with-body "https://draftkingsapi.com/api/v1/dfs/slates?sport=NBA&limit=5" \
  -H "Authorization: Bearer $DRAFTKINGS_API_KEY"

curl --fail-with-body "https://draftkingsapi.com/api/v1/dfs/players?sport=NBA&slate_id=YOUR_SLATE_ID&limit=25" \
  -H "Authorization: Bearer $DRAFTKINGS_API_KEY"

Exact semantics

Each row wraps the source record under data, next to id, sport, slate_id, observed_at and capture evidence. Field names follow the source and vary by sport, so check them rather than assuming one schema.

FieldWhat it means
data.draftableIdOne roster-slot record. One athlete can have several.
data.playerId, data.playerDkIdUse these when you mean the athlete. Deduplicating draftables by athlete throws away valid salary choices.
data.salaryThe DFS salary for this roster slot.
data.rosterSlotIdThe slot this draftable fills.
rights_status, source_url, caveatsKeep these with any copy you store.
source_updated_atNull when the source clock is unknown.

Access boundary

DFS is an authenticated beta on the canonical host. Outside that condition the route returns 403 with a message that public redistribution is pending source permission. That is a real boundary, so do not try to get around it, and call draftkingsapi.com directly rather than through a proxy that changes the host.

A 403 from a valid key still counts as a request. The keyless sample is not affected by this boundary because it has no source data.

If your product needs licensed DFS data to publish, buy that from a provider that sells it, or from the rights holder.

Coverage and freshness

The collector is configured for NBA, NFL, NHL, CFB, CBB, SOC, MMA, GOLF, TEN and LOL, and shares a limited number of draft-group requests across them in rotation. The worker targets fifteen minutes when enabled. We do not print counts here because they change. Status and the coverage report show what is stored, by sport and stat, with dates, and reliability shows what was measured.

When another provider fits better

Statements about other companies are paraphrased from their public pages as they read on 2026-11-03, and may have changed. They are the vendors' claims. We have not measured them. This site is not affiliated with any company named here. OpticOdds' DFS page describes a feed built for enterprise DFS operators source, which is a different job from reading slate salaries, and we did not find DraftKings salary data stated there.

  • SportsDataIO says it provides DFS slates with associated salaries from DraftKings, FanDuel and Yahoo, including all contest formats, and offers an API trial source. Choose it for multiple operators and a commercial data relationship.
  • STAT-API describes DraftKings and FanDuel contest results, lineups, ownership and historical salaries source. Choose it for ownership studies or long salary history.

Try it

Call the sample first. It needs no key.

curl --fail-with-body "https://draftkingsapi.com/api/v1/demo/dfs"

Check the recorded data

Questions

Why does one player appear several times?

A draftable is a roster-slot record, so one athlete can have several rows with different salaries. Keep the rows, and use playerId or playerDkId when you need the athlete.

Is a DFS salary the same as a price or a line?

No. A salary is a lineup budget value. It is not an offered line, sportsbook odds or an implied probability.

Why would a DFS request return 403?

DFS is an authenticated beta on the canonical host, and redistribution is pending source permission. Outside that condition the route returns 403. Treat it as a real boundary and do not try to bypass it.

Can I republish DraftKings salaries from this API?

A key does not give you that right. DFS rows state a rights status and redistribution rights are unverified. Resolve rights with the relevant holders before you publish.

Sources

  1. STAT-API: daily fantasy API checked 2026-11-03
  2. SportsDataIO: fantasy sports API checked 2026-11-03
  3. OpticOdds: daily fantasy sports checked 2026-11-03

Related resources

Independent service operated by DD Inc., not affiliated with or endorsed by DraftKings. Technical access is not a redistribution license. No wagering: this service does not place, recommend or settle entries or bets. Check sources and status for actual capture context.