Docs menu

OpenDota API endpoint

OpenDota record leaderboards API

Returns the top 100 single-match records for one stat (`kills`, `deaths`, `assists`, `last_hits`, `denies`, `gold_per_min`, `xp_per_min`, `hero_damage`, `tower_damage`, `hero_healing`, `duration`): rank, match id, start time, hero (with name) and the record value. Use opendota-match with a returned match id.

GETapiKey2 credits/requestOpenDota/opendota/records

Endpoint facts

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

OpenDota API for Dota 2 Data Try OpenDota record leaderboards API in Playground OpenDota API documentation

How this endpoint behaves

Returns OpenDota's top-100 single-match records for one statistic.

Header: x-api-key required.

Parameters:

field: required; allowed values: kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing, duration.

Notable response behavior:

score is the record value (for duration, seconds). Rows carry match and hero ids only; no player identities.
The set of fields was verified individually against the live API on 2026-10-28; fields that return no data are not exposed. The response is cached for up to six hours.

Sampled response

Request, 29 Oct 2026: GET /opendota/records?field=kills
Items in rows: 100
Fields filled in every checked item: 6

Field	Filled in, of 100 checked	Values in the sample
rank	100	1 to 100, median 50
match_id	100
start_time	100	2026-10-25 to 2026-10-29
hero_id	100
hero_name	100	“Wraith King” and 43 other values
score	100	56 to 114, median 60

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
field	string	Yes		Record field; one of kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing, duration Allowed values: kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing, duration.	kills

cURL example

curl -X GET "https://api.crawlora.net/api/v1/opendota/records?field=kills" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/records",
    "fetched_at": "2026-10-28T10:00:00Z",
    "field": "kills",
    "count": 1,
    "rows": [
      {
        "rank": 1,
        "match_id": 9062756621,
        "start_time": "2026-10-24T10:11:37Z",
        "hero_id": 42,
        "hero_name": "Wraith King",
        "score": 114
      }
    ]
  }
}

Request schema

No body schema

Response schema

Inline response schema

Field	Type	Required	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.RecordsResponse	No
data.count	integer	No	100
data.fetched_at	string	No	2026-10-27T10:00:00Z
data.field	string	No	kills
data.rows	array	No
data.rows[].hero_id	integer	No	42
data.rows[].hero_name	string	No	Wraith King
data.rows[].match_id	integer	No	9062756621
data.rows[].rank	integer	No	1
data.rows[].score	integer	No	114
data.rows[].start_time	string	No	2026-10-24T10:11:37Z
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
400	Bad Request	#/definitions/app.Response
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/records?field=kills" \
  -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 record leaderboards API

GETapiKey2 credits/requestOpenDota/opendota/records

Endpoint facts

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

OpenDota API for Dota 2 Data Try OpenDota record leaderboards API in Playground OpenDota API documentation

How this endpoint behaves

Returns OpenDota's top-100 single-match records for one statistic.

Header: x-api-key required.

Parameters:

field: required; allowed values: kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing, duration.

Notable response behavior:

score is the record value (for duration, seconds). Rows carry match and hero ids only; no player identities.
The set of fields was verified individually against the live API on 2026-10-28; fields that return no data are not exposed. The response is cached for up to six hours.

Sampled response

Request, 29 Oct 2026: GET /opendota/records?field=kills
Items in rows: 100
Fields filled in every checked item: 6

Field	Filled in, of 100 checked	Values in the sample
rank	100	1 to 100, median 50
match_id	100
start_time	100	2026-10-25 to 2026-10-29
hero_id	100
hero_name	100	“Wraith King” and 43 other values
score	100	56 to 114, median 60

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
field	string	Yes		Record field; one of kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing, duration Allowed values: kills, deaths, assists, last_hits, denies, gold_per_min, xp_per_min, hero_damage, tower_damage, hero_healing, duration.	kills

cURL example

curl -X GET "https://api.crawlora.net/api/v1/opendota/records?field=kills" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/records",
    "fetched_at": "2026-10-28T10:00:00Z",
    "field": "kills",
    "count": 1,
    "rows": [
      {
        "rank": 1,
        "match_id": 9062756621,
        "start_time": "2026-10-24T10:11:37Z",
        "hero_id": 42,
        "hero_name": "Wraith King",
        "score": 114
      }
    ]
  }
}

Request schema

No body schema

Response schema

Inline response schema

Field	Type	Required	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.RecordsResponse	No
data.count	integer	No	100
data.fetched_at	string	No	2026-10-27T10:00:00Z
data.field	string	No	kills
data.rows	array	No
data.rows[].hero_id	integer	No	42
data.rows[].hero_name	string	No	Wraith King
data.rows[].match_id	integer	No	9062756621
data.rows[].rank	integer	No	1
data.rows[].score	integer	No	114
data.rows[].start_time	string	No	2026-10-24T10:11:37Z
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
400	Bad Request	#/definitions/app.Response
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/records?field=kills" \
  -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 record leaderboards API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

OpenDota record leaderboards API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related