Docs menu

OpenDota API endpoint

OpenDota matches by hero lineup API

Returns recent public Dota 2 matches in which the given heroes were on team A and/or team B, with both full lineups (radiant and dire), whether Radiant won, and which side the requested team A heroes were on and whether they won. Provide at least one hero id in total; each side takes up to 5 comma-separated hero ids from opendota-heroes. Unknown or repeated hero ids return an invalid-parameter error.

GETapiKey2 credits/requestOpenDota/opendota/find-matches

Endpoint facts

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

OpenDota API for Dota 2 Data Try OpenDota matches by hero lineup API in Playground OpenDota API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

team_a: optional comma-separated hero ids (up to 5) that must be on team A, from opendota-heroes.
team_b: optional comma-separated hero ids (up to 5) that must be on team B.

Notable response behavior:

At least one hero id is required across team_a and team_b. A non-number, an id that is not in opendota-heroes, a repeated id or more than five ids on one side returns 400 before any search.
OpenDota returns each match with a fixed orientation: radiant and dire lineups (hidden slots are left out) and radiant_win. Your team_a heroes can be on either side, so each match also has team_a_side (radiant or dire) and team_a_win, worked out from where the team_a heroes were; both are omitted when team_a is empty.
The response is cached for up to five minutes.

Sampled response

Request, 29 Oct 2026: GET /opendota/find-matches?team_a=1%2C2
Items in matches: 10
Fields filled in every checked item: 7

Field	Filled in, of 10 checked	Values in the sample
match_id	10
start_time	10	2026-10-29
radiant_win	10	true in 5 of 10
radiant	10	median 5 entries
dire	10	median 5 entries
team_a_side	10	dire (6), radiant (4)
team_a_win	10	true in 5 of 10

Request parameters

Parameter	Type	Required	Description	Example
x-api-key (header)	string	Yes	API key required
team_a	string	No	Comma-separated hero ids (up to 5) that must be on team A	1,2
team_b	string	No	Comma-separated hero ids (up to 5) that must be on team B	3

cURL example

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

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/findMatches?teamA=1&teamA=2&teamB=2",
    "fetched_at": "2026-10-29T01:20:00Z",
    "team_a_hero_ids": [
      1,
      2
    ],
    "team_b_hero_ids": [
      2
    ],
    "count": 1,
    "matches": [
      {
        "match_id": 9066484102,
        "start_time": "2026-10-29T00:37:42Z",
        "radiant_win": true,
        "radiant": [
          {
            "hero_id": 3,
            "localized_name": "Bane"
          }
        ],
        "dire": [
          {
            "hero_id": 1,
            "localized_name": "Anti-Mage"
          },
          {
            "hero_id": 2,
            "localized_name": "Axe"
          }
        ],
        "team_a_side": "dire",
        "team_a_win": false
      }
    ]
  }
}

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.FindMatchesResponse	No
data.count	integer	No		20
data.fetched_at	string	No		2026-10-27T10:00:00Z
data.matches	array	No
data.matches[].dire	array	No
data.matches[].dire[].hero_id	integer	No		1
data.matches[].dire[].localized_name	string	No		Anti-Mage
data.matches[].match_id	integer	No		9066484102
data.matches[].radiant	array	No
data.matches[].radiant[].hero_id	integer	No		1
data.matches[].radiant[].localized_name	string	No		Anti-Mage
data.matches[].radiant_win	boolean	No		true
data.matches[].start_time	string	No		2026-10-29T00:37:42Z
data.matches[].team_a_side	string	No	radiant, dire	dire
data.matches[].team_a_win	boolean	No		false
data.source_url	string	No
data.team_a_hero_ids	array	No
data.team_b_hero_ids	array	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/find-matches" \
  -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 Hero Abilities API documentation OpenDota Aghanim descriptions API documentation OpenDota hero durations API documentation

Open in Playground Back to group

Docs menu

OpenDota API endpoint

OpenDota matches by hero lineup API

GETapiKey2 credits/requestOpenDota/opendota/find-matches

Endpoint facts

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

OpenDota API for Dota 2 Data Try OpenDota matches by hero lineup API in Playground OpenDota API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

team_a: optional comma-separated hero ids (up to 5) that must be on team A, from opendota-heroes.
team_b: optional comma-separated hero ids (up to 5) that must be on team B.

Notable response behavior:

At least one hero id is required across team_a and team_b. A non-number, an id that is not in opendota-heroes, a repeated id or more than five ids on one side returns 400 before any search.
OpenDota returns each match with a fixed orientation: radiant and dire lineups (hidden slots are left out) and radiant_win. Your team_a heroes can be on either side, so each match also has team_a_side (radiant or dire) and team_a_win, worked out from where the team_a heroes were; both are omitted when team_a is empty.
The response is cached for up to five minutes.

Sampled response

Request, 29 Oct 2026: GET /opendota/find-matches?team_a=1%2C2
Items in matches: 10
Fields filled in every checked item: 7

Field	Filled in, of 10 checked	Values in the sample
match_id	10
start_time	10	2026-10-29
radiant_win	10	true in 5 of 10
radiant	10	median 5 entries
dire	10	median 5 entries
team_a_side	10	dire (6), radiant (4)
team_a_win	10	true in 5 of 10

Request parameters

Parameter	Type	Required	Description	Example
x-api-key (header)	string	Yes	API key required
team_a	string	No	Comma-separated hero ids (up to 5) that must be on team A	1,2
team_b	string	No	Comma-separated hero ids (up to 5) that must be on team B	3

cURL example

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

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/findMatches?teamA=1&teamA=2&teamB=2",
    "fetched_at": "2026-10-29T01:20:00Z",
    "team_a_hero_ids": [
      1,
      2
    ],
    "team_b_hero_ids": [
      2
    ],
    "count": 1,
    "matches": [
      {
        "match_id": 9066484102,
        "start_time": "2026-10-29T00:37:42Z",
        "radiant_win": true,
        "radiant": [
          {
            "hero_id": 3,
            "localized_name": "Bane"
          }
        ],
        "dire": [
          {
            "hero_id": 1,
            "localized_name": "Anti-Mage"
          },
          {
            "hero_id": 2,
            "localized_name": "Axe"
          }
        ],
        "team_a_side": "dire",
        "team_a_win": false
      }
    ]
  }
}

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.FindMatchesResponse	No
data.count	integer	No		20
data.fetched_at	string	No		2026-10-27T10:00:00Z
data.matches	array	No
data.matches[].dire	array	No
data.matches[].dire[].hero_id	integer	No		1
data.matches[].dire[].localized_name	string	No		Anti-Mage
data.matches[].match_id	integer	No		9066484102
data.matches[].radiant	array	No
data.matches[].radiant[].hero_id	integer	No		1
data.matches[].radiant[].localized_name	string	No		Anti-Mage
data.matches[].radiant_win	boolean	No		true
data.matches[].start_time	string	No		2026-10-29T00:37:42Z
data.matches[].team_a_side	string	No	radiant, dire	dire
data.matches[].team_a_win	boolean	No		false
data.source_url	string	No
data.team_a_hero_ids	array	No
data.team_b_hero_ids	array	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/find-matches" \
  -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 matches by hero lineup API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

OpenDota matches by hero lineup API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related