DFS Data API: Player Props & Projections for Lineup Tools

A DFS data API for Australian pick'em and lineup tools: player props from the books plus Dabble's pick'em lane, then turn no-vig fair odds into projections.

Australia's DFS is pick'em: over/under on a player stat. SockOdds prices 188 player-prop markets from the sportsbooks plus Dabble's pick'em lane (dabble__pickem), all under the same oddID, with fairOdds to turn into projections.

Why use SockOdds for DFS

Sportsbook and pick'em props in one feed. One byBookmaker map per prop.
Alternate lines normalised. includeAltLines=true.
Implied projections from fair odds. fairOverUnder is a de-vigged consensus line.
Player ids. Production playerIDs joinable across books and days.
Results. Grade a pick from results where the source has them.

What you can build

Lineup optimisers

Fair lines as projections, book lines as constraints.

Pick'em and over/under tools

Compare Dabble's line to the consensus; see the player props analyzer.

Player-prop analysis

Outlier lines across books.

Example request

curl "https://api.sockodds.com/v2/events/?leagueID=AFL&oddID=disposals-PLAYER_ID-game-ou-over&includeOpposingOdds=true&bookmakerID=dabble__pickem,sportsbet,tab&limit=1" \
  -H "x-api-key: YOUR_API_KEY"

One prop type across every player, the pick'em lane next to the books:

{
  "eventID": "afl_2026-09-03_fremantle_vs_hawthorn",
  "leagueID": "AFL",
  "odds": {
    "points-all-game-eo-odd": {
      "oddID": "points-all-game-eo-odd",
      "opposingOddID": "points-all-game-eo-even",
      "marketName": "Odd/Even Total Points",
      "statID": "points",
      "statEntityID": "all",
      "periodID": "game",
      "betTypeID": "eo",
      "sideID": "odd",
      "fairOdds": null,
      "bookOdds": "-116",
      "byBookmaker": {
        "unibet": {
          "odds": "-115",
          "decimal": 1.87,
          "available": true
        },
        "tabtouch": {
          "odds": "-118",
          "decimal": 1.85,
          "available": true
        }
      }
    }
  }
}

SockOdds vs sourcing DFS data yourself

Capability	SockOdds	sourcing DFS data yourself
Sportsbook + pick'em props	One `byBookmaker` map	One integration per site
Alternate lines	Normalised	Schemas differ everywhere
Implied projections	`fairOverUnder` built in	De-vig each book yourself
Player ids	Production `playerID`s	Map by hand
Results	On the event where sourced	Join your own box scores

Frequently asked questions

What is a DFS data API in Australia?

A feed of player-prop lines from the books and pick'em apps, normalised for lineup and pick'em tools.

Does it include Dabble?

Yes — dabble and its dabble__pickem lane.

How do I turn odds into projections?

Use fairOverUnder, or de-vig the two sides of a book's line.

Can I get player stats for settlement?

Where the source carries results.

Is this a DFS contest platform?

No — data only.

How fresh are the props?

~2 minutes.

Related use cases

Odds API for Positive EV Betting: Positive EV betting API with no-vig fairOdds and every AU book's price side by side, so you can surface +EV bets without building your own devig pipeline..
Odds API for Parlay Builders: A multi and same-game-multi builder API: pull every market as a leg (props, alt lines, game markets), normalise via oddID, and compute combined odds..
Pricing: plans priced on request rate and scope, including a free Lite tier with no card.

Start building today

Free plan available. Set up in 5 minutes. Scale when you're ready.

Get your API key Explore the docs