OpenDota API endpoint
Returns a zero-based page of OpenDota team records with team IDs, names, tags, ranking and recent-match metadata. OpenDota returns up to 1000 teams per page; use `next_page` while present. Use a team ID with opendota_team or opendota_team_matches.
/opendota/teamsReturns a page of OpenDota team records with IDs, names, tags, ratings, win/loss totals, and recent-match metadata.
Header: Crawlora x-api-key required; no OpenDota API key is needed upstream.
Query parameters:
page: optional zero-based page index; defaults to 0.Notable response behavior:
next_page value to fetch the next page; it is omitted when fewer than 1,000 rows are returned.last_match_time is returned in UTC RFC 3339 format. Missing timestamps remain omitted.The array is shortened to one sample row here; count reports the full page size.
The response returned 1,000 items. Field counts and profiles examine the first 500 checked items.
| Field | Filled in, of 500 checked | Values in the sample |
|---|---|---|
| id | 500 | |
| name | 493 | “Team Yandex” and 462 other values |
| tag | 448 | “TY” and 393 other values |
| logo_url | 462 | cdn.steamusercontent.com and 3 other hosts |
| rating | 500 | 1,128.25 to 1,582.82, median 1,181.19 |
| delta | 71 | -25.91 to 24.38, median -9.7 |
| wins | 500 | 7 to 1,885, median 43 |
| losses | 500 | 0 to 1,289, median 28 |
| last_match_time | 500 | 2012-11-07 to 2026-10-28 |
| last_match_id | 71 |
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required | ||
| page | integer | No | 0 | Zero-based page index; defaults to 0 | 0 |
curl -X GET "https://api.crawlora.net/api/v1/opendota/teams?page=1" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"msg": "OK",
"data": {
"source_url": "https://api.opendota.com/api/teams?page=0",
"fetched_at": "2026-10-27T12:00:00Z",
"page": 0,
"count": 1000,
"next_page": 1,
"teams": [
{
"id": 9823272,
"name": "Team Yandex",
"tag": "TY",
"rating": 1610.13,
"delta": 5.33175,
"wins": 227,
"losses": 140,
"last_match_time": "2026-10-26T15:25:11Z",
"last_match_id": 9063026856
}
]
}
}Request schema
No body schema
Response schema
Inline response schema
| Field | Type | Required | Enum | Bounds | 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.TeamsResponse | No | ||||
| data.count | integer | No | 1000 | |||
| data.fetched_at | string | No | 2026-10-27T10:00:00Z | |||
| data.next_page | integer | No | 1 | |||
| data.page | integer | No | 0 | |||
| data.source_url | string | No | ||||
| data.teams | array | No | Team record, 10 fields: delta, id, last_match_id, last_match_time, logo_url, losses, name, rating, tag, wins. Described under OpenDota team details API. | |||
| msg | unknown | No | Msg is the message that describes the result of the request @example "Request successful" |
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/opendota/teams?page=1" \
-H "x-api-key: $CRAWLORA_API_KEY"