DFS Cookbook
Recipes for specific jobs. The API reference documents one endpoint at a time — this documents one task at a time, from the first call to the printed answer. Open any recipe to run its calls and see real rows.
Every recipe is generated from one source and compiled against the published SDKs, so the code here is the code that ships in the client libraries.
Start here
The first calls. Resolve an id, read a pool.Resolves the one slate id that every other DFS recipe needs — the operator's featured contest pool for a given day and sport.
/dfs/slates1 call you can runLists every player a slate lets you roster, with the salary the operator charged and the season average that justified it.
/dfs/slate_players1 call you can runRead the data
Real results, and the nulls that come with them.Splits a single fantasy score into the 26 scoring categories that produced it, next to the raw box-score numbers behind each one.
/dfs/player_stats1 call you can runReports what every player on a slate actually scored under that operator's own rules, and ranks them.
/dfs/slate_players/dfs/player_stats2 calls you can runBuild a view
Rank games and teams the way a lineup is built.Ranks the games in a slate's pool by the total fantasy points every player in them produced, split home and away.
/dfs/game_stats1 call you can runRanks each team on a slate by the fantasy points its players produced, with the opponent and the home or away side attached.
/dfs/team_stats1 call you can runGo deeper
Multi-hop chains and derived measures.Ranks a slate by points scored per $1,000 of salary — the value screen that decides most lineups.
/dfs/player_stats1 call you can runWalks the full contest chain to the roster that finished first — the nine players, their salaries, and the prize.
/dfs/contests/dfs/contest_user_lineups/dfs/contest_user_lineup_player_entries/dfs/slate_players2 calls you can run