PrizePicks API.
Normalized player props, one endpoint.

No. PrizePicks does not offer a public API for its props board — that is why KashRock ingests the lines for you and serves them normalized on one endpoint. Create a free Sandbox key and query GET /v6/esports/{sport}/props?book=prizepicks.

• —Player, stat type, line, direction, team, and canonical propId per prop.
• —CS2, Valorant, LoL, Dota 2, COD, R6, MLBB, Deadlock — one schema across every title.
• —Same propId across PrizePicks, Underdog, Betr & Sleeper for line comparison.

One key covers PrizePicks and the other 24 books — every row comes back on the same schema, so nothing about the read is PrizePicks-specific.

A real PrizePicks row from production — the same shape every other book returns, with the canonical propId that lets you line-shop across venues.

{
  "source": "kashrock",
  "sport": "cs2",
  "props": [
    {
      "propId": "kr_prop_da545d589900",
      "player_name": "iDISBALANCE",
      "stat_type": "CS2_HEADSHOTS_MAP_3",
      "line": 5.5,
      "odds": -110,
      "direction": "over",
      "team": "Bebop",
      "book_name": "PrizePicks",
      "event_time": "2026-09-10T13:00:00.000Z"
    }
  ]
}

• —The app's internal endpoints change without notice — the normalized schema does not
• —Player, stat, line, direction, and team arrive already mapped to canonical KashRock ids
• —The same propId lines PrizePicks up next to every other book for comparison
• —One API key and one auth header replace per-source session handling

• —Create a free Sandbox key on Pricing — $0, no card, 500 requests every UTC day
• —Call GET /v6/esports/cs2/props?book=prizepicks with the key in the X-API-Key header
• —Filter by stat_type, player, or match — the response is the board as KashRock serves it