Docs menu

OpenDota API endpoint

OpenDota live Dota 2 games API

Returns OpenDota's current top live Dota 2 games: match and league IDs, team names, score, game clock, net-worth lead, player names when exposed, raw hero IDs, the upstream team code (`0` or `1`), and team slot (`1`, `2`, `3`, `4`, or `5`). The source mixes public matchmaking with tournament games; `league_id` is `0` when no league is associated, so its presence alone does not certify a professional event. `delay_seconds` and `last_update_time` report source freshness. Live player K/D/A is not provided by this endpoint. Resolve `hero_id` values with opendota_heroes.

GETapiKey1 credit/requestOpenDota/opendota/live

Endpoint facts

Method: GET
API path: /opendota/live
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: OpenDota

OpenDota API for Dota 2 Data Try OpenDota live Dota 2 games API in Playground OpenDota API documentation

How this endpoint behaves

Header: Crawlora x-api-key required; no OpenDota API key is needed upstream.

Parameters: none.

Notable response behavior:

The response can include ordinary public matchmaking and tournament games. league_id is 0 when no league is associated; a nonzero ID does not by itself prove a professional event.
delay_seconds and last_update_time describe the source snapshot. The source is best-effort and its observed delay varied. A missing update time stays omitted; a zero timestamp remains zero.
Player team_code values are 0 and 1. team_slot values are 1, 2, 3, 4, and 5. These are raw OpenDota codes.
hero_id is an OpenDota hero identifier. Use opendota-heroes to resolve the current IDs and names.
The source does not provide live player K/D/A on this endpoint. An empty matches list is valid when no games are live.
The endpoint caches the source snapshot for up to one minute to stay within OpenDota's anonymous API limits.

Sampled response

Request, 28 Oct 2026: GET /opendota/live
Items in matches: 100
Fields filled in every checked item: 9
Fields empty in some or all items: 3

Field	Filled in, of 100 checked	Values in the sample
match_id	100
league_id	100
radiant_score	100	0 to 69, median 25
dire_score	100	0 to 74, median 26
radiant_lead	100	-35,576 to 57,020, median 89
game_time_seconds	100	-79 to 3,980, median 1,796
delay_seconds	100	60 to 300, median 120
spectators	100	0 to 285, median 4
last_update_time	100	2026-10-27 to 2026-10-28
players	98	median 10 entries
radiant_name	1
dire_name	1

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/opendota/live" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/live",
    "fetched_at": "2026-10-27T09:50:00Z",
    "count": 1,
    "matches": [
      {
        "match_id": 9063586855,
        "league_id": 19350,
        "radiant_score": 3,
        "dire_score": 3,
        "radiant_lead": 523,
        "game_time_seconds": 414,
        "delay_seconds": 10,
        "spectators": 0,
        "last_update_time": 1793055400,
        "players": [
          {
            "name": "player-name",
            "hero_id": 28,
            "team_code": 0,
            "team_slot": 1
          }
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

Inline response schema

Field	Type	Required	Enum	Example	Description
code	integer	No			Code is the HTTP status code or a custom code used to indicate the result of the request @example 200
data	opendota.LiveMatchesResponse	No
data.count	integer	No		1
data.fetched_at	string	No		2026-10-27T10:00:00Z
data.matches	array	No
data.matches[].delay_seconds	integer	No		120
data.matches[].dire_name	string	No		Team Dire
data.matches[].dire_score	integer	No		26
data.matches[].game_time_seconds	integer	No		1820
data.matches[].last_update_time	integer	No		1793055400
data.matches[].league_id	integer	No		19350
data.matches[].match_id	integer	No		9063586855
data.matches[].players	array	No
data.matches[].players[].hero_id	integer	No		93
data.matches[].players[].name	string	No		player-name
data.matches[].players[].team_code	integer	No	0, 1	0
data.matches[].players[].team_slot	integer	No	1, 2, 3, 4, 5	1
data.matches[].radiant_lead	integer	No		-500
data.matches[].radiant_name	string	No		Team Radiant
data.matches[].radiant_score	integer	No		31
data.matches[].spectators	integer	No		24
data.source_url	string	No
msg	unknown	No			Msg is the message that describes the result of the request @example "Request successful"

Failure responses

Status	Description	Schema
429	Too Many Requests	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/opendota/live" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More OpenDota endpoint docs OpenDota API for Dota 2 Data OpenDota Ability Directory API documentation OpenDota Benchmarks API documentation OpenDota constants lookup API documentation OpenDota matches by hero lineup API documentation OpenDota Hero Abilities API documentation OpenDota Aghanim descriptions API documentation

Open in Playground Back to group

Docs menu

OpenDota API endpoint

OpenDota live Dota 2 games API

GETapiKey1 credit/requestOpenDota/opendota/live

Endpoint facts

Method: GET
API path: /opendota/live
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: OpenDota

OpenDota API for Dota 2 Data Try OpenDota live Dota 2 games API in Playground OpenDota API documentation

How this endpoint behaves

Header: Crawlora x-api-key required; no OpenDota API key is needed upstream.

Parameters: none.

Notable response behavior:

The response can include ordinary public matchmaking and tournament games. league_id is 0 when no league is associated; a nonzero ID does not by itself prove a professional event.
delay_seconds and last_update_time describe the source snapshot. The source is best-effort and its observed delay varied. A missing update time stays omitted; a zero timestamp remains zero.
Player team_code values are 0 and 1. team_slot values are 1, 2, 3, 4, and 5. These are raw OpenDota codes.
hero_id is an OpenDota hero identifier. Use opendota-heroes to resolve the current IDs and names.
The source does not provide live player K/D/A on this endpoint. An empty matches list is valid when no games are live.
The endpoint caches the source snapshot for up to one minute to stay within OpenDota's anonymous API limits.

Sampled response

Request, 28 Oct 2026: GET /opendota/live
Items in matches: 100
Fields filled in every checked item: 9
Fields empty in some or all items: 3

Field	Filled in, of 100 checked	Values in the sample
match_id	100
league_id	100
radiant_score	100	0 to 69, median 25
dire_score	100	0 to 74, median 26
radiant_lead	100	-35,576 to 57,020, median 89
game_time_seconds	100	-79 to 3,980, median 1,796
delay_seconds	100	60 to 300, median 120
spectators	100	0 to 285, median 4
last_update_time	100	2026-10-27 to 2026-10-28
players	98	median 10 entries
radiant_name	1
dire_name	1

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/opendota/live" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/live",
    "fetched_at": "2026-10-27T09:50:00Z",
    "count": 1,
    "matches": [
      {
        "match_id": 9063586855,
        "league_id": 19350,
        "radiant_score": 3,
        "dire_score": 3,
        "radiant_lead": 523,
        "game_time_seconds": 414,
        "delay_seconds": 10,
        "spectators": 0,
        "last_update_time": 1793055400,
        "players": [
          {
            "name": "player-name",
            "hero_id": 28,
            "team_code": 0,
            "team_slot": 1
          }
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

Inline response schema

Field	Type	Required	Enum	Example	Description
code	integer	No			Code is the HTTP status code or a custom code used to indicate the result of the request @example 200
data	opendota.LiveMatchesResponse	No
data.count	integer	No		1
data.fetched_at	string	No		2026-10-27T10:00:00Z
data.matches	array	No
data.matches[].delay_seconds	integer	No		120
data.matches[].dire_name	string	No		Team Dire
data.matches[].dire_score	integer	No		26
data.matches[].game_time_seconds	integer	No		1820
data.matches[].last_update_time	integer	No		1793055400
data.matches[].league_id	integer	No		19350
data.matches[].match_id	integer	No		9063586855
data.matches[].players	array	No
data.matches[].players[].hero_id	integer	No		93
data.matches[].players[].name	string	No		player-name
data.matches[].players[].team_code	integer	No	0, 1	0
data.matches[].players[].team_slot	integer	No	1, 2, 3, 4, 5	1
data.matches[].radiant_lead	integer	No		-500
data.matches[].radiant_name	string	No		Team Radiant
data.matches[].radiant_score	integer	No		31
data.matches[].spectators	integer	No		24
data.source_url	string	No
msg	unknown	No			Msg is the message that describes the result of the request @example "Request successful"

Failure responses

Status	Description	Schema
429	Too Many Requests	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/opendota/live" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

Open in Playground Back to group

OpenDota live Dota 2 games API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

OpenDota live Dota 2 games API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related