Frequently asked questions
Short answers about the data, plans, billing, your license, DFS data and NFL projections.
NFL projections
Which engine made the projections I receive?
The projections response carries a _metadata block. engine_version names the engine that made the rows, and served_source names the source. The default source, STAT_API_LATEST, always points to the newest STAT-API engine. When the newest engine has no rows for a slate, the response falls back to the previous engine and says so with fallback: true. The fields do not change between engines.
When do projections change?
We publish new values when a player's injury or active status changes and when our market inputs (lines and player props) change. Each row's last_update_time gives the time of its last change.
Which endpoints give a slate's projections and player pool?
GET /api/v1/dfs/slates/{slate_id}/projections?format=flat for the projections, and GET /api/v1/dfs/slate_players?slate_id={slate_id} for the pool with salaries. Use the internal slate_id from GET /api/v1/dfs/slates, not the operator's draft group ID.
What does a projection of 0 mean?
The player has no expected role: inactive, on injured reserve, on the practice squad, or deep on the depth chart. DST and K always carry a projection. The computed block of each projections response counts the slate's eligible, projected and missing players.
Still have a question? Send us the endpoint, the slate or contest ID, and the time (UTC). We reply by email, usually within one business day. Contact support →