Docs menu
BO3 API endpoint
BO3.gg forum categories API
Returns the BO3.gg forum categories of one game (id, slug and title, ordered by id; CS2 has CS2, IDEAS AND BUGS and OFF TOP) that the `category` filter of bo3-forum accepts.
GETapiKey1 credit/requestBO3
BO3/bo3/forum-categoriesEndpoint facts
- Method
- GET
- API path
- /bo3/forum-categories
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- BO3
How this endpoint behaves
Header: x-api-key required.
Parameters:
game: optional; allowed values:cs2,valorant,lol,dota2,r6siege,mlbb. Defaults tocs2.
Notable response behavior:
- The list is read live per game, so it follows the site; a game without a forum returns an empty list. The response is cached for up to one day.
Sampled response
- Request, 29 Oct 2026
- GET /bo3/forum-categories?game=cs2
- Items in categories
- 3
- Fields filled in every checked item
- 3
| Field | Filled in, of 3 checked | Values in the sample |
|---|---|---|
| id | 3 | |
| slug | 3 | |
| title | 3 | “CS2” and 2 other values |
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/forum-categories?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/forum-categories",
"fetched_at": "2026-10-28T10:00:00Z",
"game": "cs2",
"count": 2,
"categories": [
{
"id": 1,
"slug": "cs-2",
"title": "CS2"
},
{
"id": 4,
"slug": "ideas-and-bugs1",
"title": "IDEAS AND BUGS"
}
]
}
}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 | bo3.ForumCategoriesResponse | No | ||||
| data.categories | array | No | ||||
| data.categories[].id | integer | No | 1 | |||
| data.categories[].slug | string | No | cs-2 | |||
| data.categories[].title | string | No | CS2 | |||
| data.count | integer | No | 3 | |||
| data.fetched_at | string | No | 2026-10-28T10:00:00Z | |||
| data.game | string | No | cs2 | |||
| 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 |
| 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/forum-categories?game=cs2" \
-H "x-api-key: $CRAWLORA_API_KEY"Shared guides
Related
More BO3 endpoint docsBO3.gg Esports Data APIBO3.gg CS2 economy baseline API documentationBO3.gg forum threads API documentationBO3.gg match maps and rounds API documentationBO3.gg esports match history API documentationBO3.gg per-player match statistics API documentationBO3.gg match detail API documentation