GetPicks API.
GetPicks esports props, normalized.

Quick answer: GetPicks More/Less props are live on KashRock: CS2, LoL, and Dota 2 player kills, deaths, and assists across per-map and map-range lines, on the same canonical player and prop ids as the other DFS books. One key, GET /v7/{sport}/props.

No app session, no cookie refresh, no mobile capture on your request path: the workers already did it. Your call reads the board they published.

What GetPicks posts

GetPicks posts More/Less lines on CS2, LoL, and Dota 2 player stats (Valorant when the board lists it): kills, deaths, and assists per map and across map ranges, each with a line and a price. The board lands as prop rows on /props with the same canonical players as the other DFS books.

Where GetPicks shows up

  • : /props: The GetPicks line, direction and price per player next to every other book's row for the same prop, with the board's row count and age in seconds on every call.
  • : /flow: Money-behind, steam and shift plays flag GetPicks-led moves the same way as any other book on the board.
  • : /meta: The registry entry reports key, kind (dfs), and the live markets GetPicks posts, exactly as the API reports it.

Endpoints

GetPicks is read through the shared v7 surface: no book-specific integration, one X-API-Key header on every call.

EndpointWhat it returnsKey filter
GET /v7/{sport}/propsPer-book prop lines and the grouped viewbook row: getpicks
GET /v7/{sport}/flowSteam, shift, volume and whale plays where GetPicks moves leadkind=steam|shift|volume|whale
GET /v7/metaThe registry entry: key, kind, supported marketskey=getpicks

Live in the book registry

The real /v7/meta entry: the key, kind, and what the book supports, exactly as the API reports it.

GET /v7/meta?fields=books
{
  "book_id": 909,
  "key": "getpicks",
  "display_name": "GetPicks",
  "status": "active",
  "aliases": [
    "get picks",
    "go.getpicks",
    "getpicks.app"
  ],
  "logo": "https://www.kashrock.com/logos/getpicks.png"
}

Reading it honestly

The books object on the props response reports GetPicks's prop count on every call, prop_count: 0 when nothing is posted. An empty board is an answer, not an error.

Start in minutes

  • : Create a free Sandbox key on Pricing : $0, no card, 1,500 credits every UTC day
  • : Call GET /v7/{sport}/props?book=getpicks
  • : Grade settled picks on GET /v7/{sport}/results: hit, miss, or push with open and close

Quick reference

FieldValue
Book keybook=getpicks
Surfaces/props, /players, /results
Registry/v7/meta key=getpicks
PlanSandbox $0 for props; consensus lines from $29.99/mo

If you need a normalized feed instead of another UI wrapper, the esports api exposes live boards, schedules, and history on one schema: with the IDs and outcome patterns that keep backtests and grading honest. Start free on Sandbox, or see published pricing.

Frequently asked questions

Can I get GetPicks esports props through an API?

Yes. GetPicks More/Less lines are served on the same schema as every other DFS book. Call GET /v7/{sport}/props?book=getpicks and read the getpicks rows on the same canonical player as the rest of the board.

Which markets does GetPicks cover?

CS2, LoL, and Dota 2 player kills, deaths, and assists per map and across map ranges, with Valorant when the board lists it. Each prop carries the line, over/under direction, and price.

Can I line-shop GetPicks against other books?

Yes. GetPicks props share the canonical propId of the same player and market on other books, so comparing prices against PrizePicks, Underdog, and Betr is a filter, not a re-map.

KashRock is an independent data provider and is not affiliated with, endorsed by, or sponsored by GetPicks. Publicly available lines, normalized for informational use.