Neds API.
Neds esports lines, normalized.

Quick answer: Neds esports odds are live on KashRock: match winner lines for CS2, League of Legends, Dota 2 and Valorant, prematch and in-play, on the same canonical ids as the other books. One key, GET /v7/{sport}/lines.

No session juggling, no cookie refresh, no neds scrape on your request path: the workers already did it. Your call reads the board they published.

What Neds posts

Neds posts esports match winner markets across the major titles. Every price lands on the same canonical ids as the rest of the line books, prematch and in-play on one board.

Where Neds shows up

  • : /lines: Neds' price per market next to the consensus fair price, the books object reports its row count and age in seconds on every call.
  • : /parlays: Name neds as the leg book and price a ticket or discover +EV parlays against the rest of the market.
  • : /flow: When neds moves a number first, the shift and steam plays record which venue led and how far the price ran.

Endpoints

Neds is read through the shared v7 surface: no book-specific integration, no upstream fetch on the request path.

EndpointWhat it returnsKey filter
GET /v7/{sport}/linesPer-book prices and the consensus view for every market Neds postsbook row: neds
GET /v7/{sport}/parlaysPrice or discover parlays with neds as the leg bookbook=neds
GET /v7/{sport}/flowSteam, shift, volume and whale plays where neds moves leadkind=steam|shift|volume|whale
GET /v7/metaThe registry entry: key, kind, supported marketskey=neds

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": 700,
  "key": "neds",
  "display_name": "Neds",
  "status": "active",
  "aliases": [
    "neds",
    "neds.com.au",
    "neds online"
  ],
  "logo": "https://www.kashrock.com/logos/neds.png"
}

Reading it honestly

The booksobject on /lines reports each venue's presence, row count, and age in seconds on every call. When Neds has nothing posted for a board, the response says so instead of hiding the gap: an empty board is an answer, not an error.

Start in minutes

  • : Create a key on Pricing : Sandbox is $0; book lines need Hobby and up
  • : Call GET /v7/{sport}/lines and read the neds rows
  • : Compare against the consensus fair price on the same kr_match_id

Quick reference

FieldValue
Book keybook=neds
Surfaces/lines, /parlays, /flow
Registry/v7/meta key=neds
PlanHobby and up, 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 Neds esports odds through an API?

Yes. Neds esports match winner markets are ingested into the same schema as every other book. Call GET /v7/{sport}/lines and read the neds rows alongside the rest of the line books, on the same kr_match_id.

Which endpoints serve Neds lines?

Three: GET /v7/{sport}/lines for per-book prices and the consensus view, GET /v7/{sport}/parlays to price or discover parlays with neds as the leg book, and GET /v7/{sport}/flow for steam, shift, volume and whale plays where neds moves lead the market.

Do I have to scrape Neds myself?

No. There is no upstream fetch on the request path, workers fill the cache and your call reads it, so a response is a read, not a scrape. One X-API-Key header covers neds and the other books.

What if Neds has no lines for a sport right now?

The books object on /lines reports each venue's presence, row count and age in seconds. neds present: false simply means nothing is posted for that board, the response stays honest instead of hiding the gap.

Which plan do I need for Neds lines?

Hobby ($29.99/mo) and up, the same plan that unlocks /lines, /parlays and /flow for every line book.

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