Docs menu

OpenDota API endpoint

OpenDota team details API

Returns one team's OpenDota profile, tag, logo, rating, wins, losses and most recent match metadata.

GETapiKey1 credit/requestOpenDota/opendota/team

Endpoint facts

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

OpenDota API for Dota 2 Data Try OpenDota team details API in Playground OpenDota API documentation

How this endpoint behaves

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

Query parameters:

team_id: required positive OpenDota team ID from opendota-teams or a match response.

Notable response behavior:

Numeric team metadata is preserved when supplied. Optional values remain omitted when OpenDota has no value.
last_match_time is UTC in RFC 3339 format.
Unknown team IDs return not found.
Team detail is cached for up to one hour.

Optional fields such as logo_url are omitted from this compact example.

Sampled response

Request, 29 Oct 2026: GET /opendota/team?team_id=8255888
Fields returned with a value: 10

Field	In the sample	Value in the sample
team.id	Has a value
team.name	Has a value	“BETBOOM TEAM”
team.tag	Has a value	“BETBOOM”
team.logo_url	Has a value	cdn.steamusercontent.com
team.rating	Has a value	1,224.29
team.delta	Has a value	-21.94
team.wins	Has a value	707
team.losses	Has a value	561
team.last_match_time	Has a value	2026-10-27
team.last_match_id	Has a value

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
team_id	integer	Yes		Positive OpenDota team ID from opendota_teams or a match response	8255888

cURL example

curl -X GET "https://api.crawlora.net/api/v1/opendota/team?team_id=8255888" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/teams/8255888",
    "fetched_at": "2026-10-27T12:00:00Z",
    "team": {
      "id": 8255888,
      "name": "BETBOOM TEAM",
      "tag": "BETBOOM",
      "rating": 1271.94,
      "delta": 9.26499,
      "wins": 707,
      "losses": 559,
      "last_match_time": "2026-10-26T20:56:07Z",
      "last_match_id": 9063495955
    }
  }
}

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.TeamResponse	No
data.fetched_at	string	No	2026-10-27T10:00:00Z
data.source_url	string	No
data.team	opendota.Team	No
data.team.delta	number	No	4.2
data.team.id	integer	No	8255888
data.team.last_match_id	integer	No	9063495955
data.team.last_match_time	string	No	2026-10-26T20:56:07Z
data.team.logo_url	string	No	https://cdn.opendota.com/team-logo.png
data.team.losses	integer	No	559
data.team.name	string	No	BETBOOM TEAM
data.team.rating	number	No	1271.94
data.team.tag	string	No	BETBOOM
data.team.wins	integer	No	707
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
404	Not Found	#/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/team?team_id=8255888" \
  -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 team details API

Returns one team's OpenDota profile, tag, logo, rating, wins, losses and most recent match metadata.

GETapiKey1 credit/requestOpenDota/opendota/team

Endpoint facts

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

OpenDota API for Dota 2 Data Try OpenDota team details API in Playground OpenDota API documentation

How this endpoint behaves

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

Query parameters:

team_id: required positive OpenDota team ID from opendota-teams or a match response.

Notable response behavior:

Numeric team metadata is preserved when supplied. Optional values remain omitted when OpenDota has no value.
last_match_time is UTC in RFC 3339 format.
Unknown team IDs return not found.
Team detail is cached for up to one hour.

Optional fields such as logo_url are omitted from this compact example.

Sampled response

Request, 29 Oct 2026: GET /opendota/team?team_id=8255888
Fields returned with a value: 10

Field	In the sample	Value in the sample
team.id	Has a value
team.name	Has a value	“BETBOOM TEAM”
team.tag	Has a value	“BETBOOM”
team.logo_url	Has a value	cdn.steamusercontent.com
team.rating	Has a value	1,224.29
team.delta	Has a value	-21.94
team.wins	Has a value	707
team.losses	Has a value	561
team.last_match_time	Has a value	2026-10-27
team.last_match_id	Has a value

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
team_id	integer	Yes		Positive OpenDota team ID from opendota_teams or a match response	8255888

cURL example

curl -X GET "https://api.crawlora.net/api/v1/opendota/team?team_id=8255888" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/teams/8255888",
    "fetched_at": "2026-10-27T12:00:00Z",
    "team": {
      "id": 8255888,
      "name": "BETBOOM TEAM",
      "tag": "BETBOOM",
      "rating": 1271.94,
      "delta": 9.26499,
      "wins": 707,
      "losses": 559,
      "last_match_time": "2026-10-26T20:56:07Z",
      "last_match_id": 9063495955
    }
  }
}

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.TeamResponse	No
data.fetched_at	string	No	2026-10-27T10:00:00Z
data.source_url	string	No
data.team	opendota.Team	No
data.team.delta	number	No	4.2
data.team.id	integer	No	8255888
data.team.last_match_id	integer	No	9063495955
data.team.last_match_time	string	No	2026-10-26T20:56:07Z
data.team.logo_url	string	No	https://cdn.opendota.com/team-logo.png
data.team.losses	integer	No	559
data.team.name	string	No	BETBOOM TEAM
data.team.rating	number	No	1271.94
data.team.tag	string	No	BETBOOM
data.team.wins	integer	No	707
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
404	Not Found	#/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/team?team_id=8255888" \
  -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 team details API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

OpenDota team details API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related