{"id":4414,"date":"2026-10-05T10:00:00","date_gmt":"2026-10-05T10:00:00","guid":{"rendered":"https:\/\/oddspapi.io\/blog\/?p=4414"},"modified":"2026-09-23T15:24:58","modified_gmt":"2026-09-23T15:24:58","slug":"esports-results-api","status":"publish","type":"post","link":"https:\/\/oddspapi.io\/blog\/esports-results-api\/","title":{"rendered":"Esports Results API: Settle 303 CS2, LoL and Dota 2 Series"},"content":{"rendered":"

Looking for an esports results API? You need the final score of a CS2, League of Legends or Dota 2 series, keyed to the same fixture ID as the odds you bet into. Most esports data products sell one or the other. The stats vendors sell scores and player telemetry. The odds feeds sell prices and forget the fixture once it finishes.<\/p>\n

OddsPapi returns both on one free key. \/v4\/scores<\/code> gives the series score and, on LoL and Dota 2, the map-by-map result. \/v4\/settlements<\/code> grades every Winner, Maps Handicap and Total Maps outcome. \/v4\/historical-odds<\/code> replays the closing price on the same fixture ID. This guide runs all three over every CS2, LoL and Dota 2 fixture that finished between 13 and 23 September 2026, measured on 23 September.<\/p>\n

The result: 303 decided series<\/strong>, a self-built grader that agreed with \/v4\/settlements<\/code> on 2,520 of 2,520 outcomes<\/strong>, and a closing favourite that won 69.6% of the time on Pinnacle’s price. If you only need live esports prices, the esports odds API guide<\/a> covers the board. This post picks up after the final map.<\/p>\n

Why esports results and esports odds usually live in two products<\/h2>\n

The esports stats vendors built their products for broadcasters and team analysts. You get kills, rounds and player telemetry on their own fixture IDs, and you map those IDs to your odds by hand. The PandaScore comparison<\/a> covers what a stats plan does and does not include. The generic odds APIs carry the price and drop the fixture once it finishes, so you grade your own bets by hand.<\/p>\n

That gap hurts in three places: settling a bet, labelling a training set, and auditing your closing line value. Each one needs the price and the result on the same key.<\/p>\n

\n\n\n\n\n\n\n\n\n\n
Job<\/th>\nStats vendor plus odds feed<\/th>\nOddsPapi, measured 23 September 2026<\/th>\n<\/tr>\n<\/thead>\n
Series score<\/td>\nStats API, separate fixture IDs to map<\/td>\n\/v4\/scores<\/code>: 303 CS2, LoL and Dota 2 series<\/td>\n<\/tr>\n
Map-by-map score<\/td>\nStats API<\/td>\n\/v4\/scores<\/code> p1<\/code> to p5<\/code>: 68 Dota 2 and 41 LoL series<\/td>\n<\/tr>\n
Graded bets<\/td>\nYour own code<\/td>\n\/v4\/settlements<\/code>: 2,220 decided outcomes on 45 series checked<\/td>\n<\/tr>\n
Closing price<\/td>\nA second vendor, if it keeps history<\/td>\n\/v4\/historical-odds<\/code>: 266 series with a closing Winner price<\/td>\n<\/tr>\n
Fixture ID shared with the odds<\/td>\nNo, you map two ID systems<\/td>\nYes, one fixtureId<\/code> on all four endpoints<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n

Step 1: pull the played fixtures<\/h2>\n

Esports sit under their own sport IDs: 16 is Dota 2, 17 is Counter-Strike and 18 is League of Legends. \/v4\/fixtures<\/code> rejects a sportId<\/code>-only range wider than ten days, so the window below is exactly ten. Treat a 404 as an empty window. The key goes in the query string, never in a header.<\/p>\n

import os, time, requests\nfrom datetime import datetime, timedelta, timezone\n\nAPI_KEY = os.environ["ODDSPAPI_API_KEY"]\nBASE = "https:\/\/api.oddspapi.io\/v4"\n\ndef get(path, **params):\n    """GET with the key as a query parameter; honours retryMs on a 429."""\n    params["apiKey"] = API_KEY\n    for attempt in range(6):\n        r = requests.get(f"{BASE}\/{path}", params=params, timeout=120)\n        if r.status_code == 429:\n            time.sleep(r.json()["error"].get("retryMs", 1000) \/ 1000 + 0.5)\n            continue\n        time.sleep(1.1)\n        return r\n    return r\n\nESPORTS = {16: "Dota 2", 17: "CS2", 18: "LoL"}\nend = datetime(2026, 9, 23, tzinfo=timezone.utc)\nstart = end - timedelta(days=10)          # \/fixtures caps a sportId-only range at 10 days\n\nplayed = []\nfor sport_id, name in ESPORTS.items():\n    r = get("fixtures", sportId=sport_id,\n            **{"from": start.strftime("%Y-%m-%d"), "to": end.strftime("%Y-%m-%d")})\n    if r.status_code == 404:              # an empty window, not an error\n        continue\n    for f in r.json():\n        if f.get("statusName") == "Finished":\n            f["esport"] = name\n            played.append(f)\n\nprint(len(played), "finished fixtures between", start.date(), "and", end.date())\nfor name in ESPORTS.values():\n    print(f"  {name:7s}", sum(f["esport"] == name for f in played))<\/code><\/pre>\n
305 finished fixtures between 2026-09-13 and 2026-09-23\n  Dota 2  69\n  CS2     180\n  LoL     56<\/code><\/pre>\n
Keep only statusName == \"Finished\"<\/code>. A series that still reads Live<\/code> can carry a part-played score such as 1-0<\/code> in a best-of-three, and a grader would settle it early.<\/p>\n
Step 2: read the score in all three shapes<\/h2>\n
\/v4\/scores<\/code> nests everything under scores.periods<\/code>. result<\/code> holds the series score as maps won. What sits next to it depends on the title and the series length:<\/p>\n