Docs menu

BO3 API endpoint

BO3.gg team ranking dates API

Returns the days for which Valve published an official ranking for a game (newest first) and the region labels BO3.gg accepts for that game's team rankings. Use it to choose `date` and `region` for bo3-team-rankings.

GETapiKey1 credit/requestBO3/bo3/team-ranking-dates

Endpoint facts

Method: GET
API path: /bo3/team-ranking-dates
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: BO3

BO3.gg Esports Data API Try BO3.gg team ranking dates API in Playground BO3 API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

game: optional; allowed values: cs2, valorant, lol, dota2, r6siege, mlbb. Defaults to cs2.

Notable response behavior:

dates are official ranking days in YYYY-MM-DD, newest first (CS2 has about 60, from 2023-08-29); regions are the labels bo3-team-rankings accepts for that game:
- cs2: Europe, Americas, Asia.
- valorant: EMEA, Americas, Pacific.
- lol: Europe, Americas, Asia.
- dota2: Western Europe, Eastern Europe, China, North America, South America, Southeast Asia.
- r6siege: Europe, North America, South America, Asia-Pacific.
- mlbb: Southeast Asia, North America, Europe, Latin America, Middle East & Africa, East Asia.
Games without an official Valve list return an empty dates list. The response is cached for up to one day.

Sampled response

Request, 29 Oct 2026: GET /bo3/team-ranking-dates?game=cs2
Fields returned with a value: 4

Field	In the sample	Value in the sample
game	Has a value	“cs2”
count	Has a value	59
dates	Has a value	59 entries
regions	Has a value	3 entries

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
game	string	No	cs2	Game; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to cs2 Allowed values: cs2, valorant, lol, dota2, r6siege, mlbb.

cURL example

curl -X GET "https://api.crawlora.net/api/v1/bo3/team-ranking-dates?game=cs2" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.bo3.gg/api/v1/team-ranking-dates",
    "fetched_at": "2026-10-28T10:00:00Z",
    "game": "cs2",
    "count": 2,
    "dates": [
      "2026-10-05",
      "2026-08-03"
    ],
    "regions": [
      "Europe",
      "Americas",
      "Asia"
    ]
  }
}

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	bo3.TeamRankingDatesResponse	No
data.count	integer	No	59
data.dates	array	No
data.fetched_at	string	No	2026-10-28T10:00:00Z
data.game	string	No	cs2
data.regions	array	No
data.source_url	string	No	https://bo3.gg/matches/current
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/bo3/team-ranking-dates?game=cs2" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More BO3 endpoint docs BO3.gg Esports Data API BO3.gg CS2 economy baseline API documentation BO3.gg forum categories API documentation BO3.gg forum threads API documentation BO3.gg match maps and rounds API documentation BO3.gg esports match history API documentation BO3.gg per-player match statistics API documentation

Open in Playground Back to group

Docs menu

BO3 API endpoint

BO3.gg team ranking dates API

GETapiKey1 credit/requestBO3/bo3/team-ranking-dates

Endpoint facts

Method: GET
API path: /bo3/team-ranking-dates
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: BO3

BO3.gg Esports Data API Try BO3.gg team ranking dates API in Playground BO3 API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

game: optional; allowed values: cs2, valorant, lol, dota2, r6siege, mlbb. Defaults to cs2.

Notable response behavior:

dates are official ranking days in YYYY-MM-DD, newest first (CS2 has about 60, from 2023-08-29); regions are the labels bo3-team-rankings accepts for that game:
- cs2: Europe, Americas, Asia.
- valorant: EMEA, Americas, Pacific.
- lol: Europe, Americas, Asia.
- dota2: Western Europe, Eastern Europe, China, North America, South America, Southeast Asia.
- r6siege: Europe, North America, South America, Asia-Pacific.
- mlbb: Southeast Asia, North America, Europe, Latin America, Middle East & Africa, East Asia.
Games without an official Valve list return an empty dates list. The response is cached for up to one day.

Sampled response

Request, 29 Oct 2026: GET /bo3/team-ranking-dates?game=cs2
Fields returned with a value: 4

Field	In the sample	Value in the sample
game	Has a value	“cs2”
count	Has a value	59
dates	Has a value	59 entries
regions	Has a value	3 entries

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
game	string	No	cs2	Game; one of cs2, valorant, lol, dota2, r6siege, mlbb; defaults to cs2 Allowed values: cs2, valorant, lol, dota2, r6siege, mlbb.

cURL example

curl -X GET "https://api.crawlora.net/api/v1/bo3/team-ranking-dates?game=cs2" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.bo3.gg/api/v1/team-ranking-dates",
    "fetched_at": "2026-10-28T10:00:00Z",
    "game": "cs2",
    "count": 2,
    "dates": [
      "2026-10-05",
      "2026-08-03"
    ],
    "regions": [
      "Europe",
      "Americas",
      "Asia"
    ]
  }
}

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	bo3.TeamRankingDatesResponse	No
data.count	integer	No	59
data.dates	array	No
data.fetched_at	string	No	2026-10-28T10:00:00Z
data.game	string	No	cs2
data.regions	array	No
data.source_url	string	No	https://bo3.gg/matches/current
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/bo3/team-ranking-dates?game=cs2" \
  -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

BO3.gg team ranking dates API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

BO3.gg team ranking dates API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related