CS2 headshot props: who posts what, and where the gaps are

What a headshot prop is grading

A headshot prop is not a kills prop with a different name. It counts only kills that land as headshots, a number that tracks aim form, role and opponent more than raw volume. That is why books price it separately, and why the same player can sit at 19.5 kills and 8.5 headshots on the same map.

Scope decides settlement. A per-map line like CS2_HEADSHOTS_MAP_3 is void unless the series goes the distance. A guaranteed-map line like CS2_HEADSHOTS_MAPS_1_2 grades on maps one and two, which are always played, so the pick settles in a 2-0. Same player, same stat, different product.

Coverage is a matrix, not a yes or no

Ask "who posts CS2 headshot props" and the honest answer is a table, which is the one above: seven books cover the guaranteed maps 1-2 span, but per-map depth thins fast. Only three books post map-2 headshots, and on the board checked 3 November 2026 Chalkboard was the only book posting map-3 headshot lines at all, 100 rows deep on each of the three maps.

{
  "source": "kashrock",
  "sport": "cs2",
  "board": "dfs",
  "props": [
    {
      "book_name": "Chalkboard",
      "propId": "kr_prop_a266cd6d3945",
      "player_name": "JamYoung",
      "stat_type": "CS2_HEADSHOTS_MAP_2",
      "line": 8.5,
      "direction": "over",
      "decimal_odds": 1.8868,
      "team": "TyLoo",
      "opponent": "Team Liquid",
      "canonical_event_id": "kr_ev_494d81146736",
      "kr_match_id": "kr_cs2_team-liquid-vs-tyloo-04-11-2026",
      "event_time": "2026-11-04T02:00:00.000Z"
    }
  ]
}

That is a real row off the live board: JamYoung, 8.5 headshots on map 2, over at 1.887 decimal, TyLoo vs Team Liquid. The offers on the same market join on the canonical player, stat type and event, so a soft line shows up as a filter result, not a manual cross-check.

Pull every headshot line in one call

Filter market on the headshot stat type and the whole board's rows for it come back together, every book, one schema:

curl -s -H "X-API-Key: $KASHROCK_API_KEY" \
  "https://kashrock.up.railway.app/v7/cs2/props?market=CS2_HEADSHOTS_MAP_2"

import { KashRock } from "kashrock"

const kr = new KashRock(process.env.KASHROCK_API_KEY)
const { props } = await kr.props("cs2", { market: "CS2_HEADSHOTS_MAP_2" })
for (const p of props) console.log(p.book_name, p.player_name, p.direction, p.line, p.decimal_odds)

Why the guaranteed span changes the bet

A per-map headshot over on map 3 needs two things: the player to hit the number and the series to reach the decider. The guaranteed-map version removes the second leg entirely. When a book prices the span instead of the single map, you are betting the player's output, not the bracket's.

Because the span pools two maps of attempts, the line lands higher than a single-map number, and the books that post it are making a different statement about volume. Compare it against the same player's per-map lines and the implied per-map rate is right there. The Chalkboard API page covers the book's stat map, and CS2 props API is the market reference.