Docs menu

BO3 API endpoint

BO3.gg per-player match statistics API

Returns every player's statistics for one BO3.gg match, ordered by team then nickname: kills, deaths, assists, headshots, first kills and deaths, trades, KAST, rating, ADR, damage, utility and money figures as a numeric `stats` map, plus the multikill counts (2K to 5K), team and opponent. The match slug comes from bo3-match-history.

GETapiKey1 credit/requestBO3/bo3/match-players

Endpoint facts

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

BO3.gg Esports Data API Try BO3.gg per-player match statistics API in Playground BO3 API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

slug: required match slug from bo3-match-history, lowercase letters, digits and hyphens.

Notable response behavior:

stats is a pass-through of the numeric columns BO3.gg reports for the game (for CS2: kills, death, assists, headshots, first_kills, first_death, trade_kills, trade_death, kast, player_rating, adr, damage, hits, shots, utility_value, money_spent, clutches and more); identifiers are not included.
multikills maps 2, 3, 4 and 5 to the number of rounds with that many kills. A match with no statistics yet (for example an upcoming one) returns an empty list or 404. The response is cached for up to ten minutes.

Sampled response

Request, 29 Oct 2026: GET /bo3/match-players?slug=vitality-vs-natus-vincere-27-10-2026
Items in players: 10
Fields filled in every checked item: 6

Field	Filled in, of 10 checked	Values in the sample
player_id	10
nickname	10
team	10	Natus Vincere (5), Team Vitality (5)
opponent	10	Team Vitality (5), Natus Vincere (5)
stats	10
multikills	10

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
slug	string	Yes		Match slug from bo3-match-history, for example vitality-vs-natus-vincere-27-10-2026	vitality-vs-natus-vincere-27-10-2026

cURL example

curl -X GET "https://api.crawlora.net/api/v1/bo3/match-players?slug=vitality-vs-natus-vincere-27-10-2026" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.bo3.gg/api/v1/match-players",
    "fetched_at": "2026-10-28T10:00:00Z",
    "slug": "vitality-vs-natus-vincere-27-10-2026",
    "count": 1,
    "players": [
      {
        "player_id": 18452,
        "nickname": "ZywOo",
        "team": "Team Vitality",
        "opponent": "Natus Vincere",
        "stats": {
          "kills": 32,
          "death": 23,
          "assists": 13,
          "kast": 0.76,
          "player_rating": 7.42,
          "adr": 92.67
        },
        "multikills": {
          "2": 6,
          "3": 3,
          "4": 0,
          "5": 0
        }
      }
    ]
  }
}

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.MatchPlayersResponse	No
data.count	integer	No	10
data.fetched_at	string	No	2026-10-28T10:00:00Z
data.players	array	No
data.players[].multikills	object	No
data.players[].nickname	string	No	ZywOo
data.players[].opponent	string	No	Natus Vincere
data.players[].player_id	integer	No	18452
data.players[].stats	object	No
data.players[].team	string	No	Team Vitality
data.players[].win	boolean	No
data.slug	string	No	vitality-vs-natus-vincere-27-10-2026
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/match-players?slug=vitality-vs-natus-vincere-27-10-2026" \
  -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 match detail API documentation

Open in Playground Back to group

Docs menu

BO3 API endpoint

BO3.gg per-player match statistics API

GETapiKey1 credit/requestBO3/bo3/match-players

Endpoint facts

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

BO3.gg Esports Data API Try BO3.gg per-player match statistics API in Playground BO3 API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

slug: required match slug from bo3-match-history, lowercase letters, digits and hyphens.

Notable response behavior:

stats is a pass-through of the numeric columns BO3.gg reports for the game (for CS2: kills, death, assists, headshots, first_kills, first_death, trade_kills, trade_death, kast, player_rating, adr, damage, hits, shots, utility_value, money_spent, clutches and more); identifiers are not included.
multikills maps 2, 3, 4 and 5 to the number of rounds with that many kills. A match with no statistics yet (for example an upcoming one) returns an empty list or 404. The response is cached for up to ten minutes.

Sampled response

Request, 29 Oct 2026: GET /bo3/match-players?slug=vitality-vs-natus-vincere-27-10-2026
Items in players: 10
Fields filled in every checked item: 6

Field	Filled in, of 10 checked	Values in the sample
player_id	10
nickname	10
team	10	Natus Vincere (5), Team Vitality (5)
opponent	10	Team Vitality (5), Natus Vincere (5)
stats	10
multikills	10

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
slug	string	Yes		Match slug from bo3-match-history, for example vitality-vs-natus-vincere-27-10-2026	vitality-vs-natus-vincere-27-10-2026

cURL example

curl -X GET "https://api.crawlora.net/api/v1/bo3/match-players?slug=vitality-vs-natus-vincere-27-10-2026" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.bo3.gg/api/v1/match-players",
    "fetched_at": "2026-10-28T10:00:00Z",
    "slug": "vitality-vs-natus-vincere-27-10-2026",
    "count": 1,
    "players": [
      {
        "player_id": 18452,
        "nickname": "ZywOo",
        "team": "Team Vitality",
        "opponent": "Natus Vincere",
        "stats": {
          "kills": 32,
          "death": 23,
          "assists": 13,
          "kast": 0.76,
          "player_rating": 7.42,
          "adr": 92.67
        },
        "multikills": {
          "2": 6,
          "3": 3,
          "4": 0,
          "5": 0
        }
      }
    ]
  }
}

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.MatchPlayersResponse	No
data.count	integer	No	10
data.fetched_at	string	No	2026-10-28T10:00:00Z
data.players	array	No
data.players[].multikills	object	No
data.players[].nickname	string	No	ZywOo
data.players[].opponent	string	No	Natus Vincere
data.players[].player_id	integer	No	18452
data.players[].stats	object	No
data.players[].team	string	No	Team Vitality
data.players[].win	boolean	No
data.slug	string	No	vitality-vs-natus-vincere-27-10-2026
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/match-players?slug=vitality-vs-natus-vincere-27-10-2026" \
  -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 per-player match statistics 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 per-player match statistics API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related