Docs menu

VLR API endpoint

VLR.gg player match history API

Returns a player's match history from VLR.gg, 50 per page, newest first: event, stage, the player's team and opponent, series score, win or loss and date. Use vlr-match with a returned `id` for the player's map statistics.

GETapiKey1 credit/requestVLR/vlr/player-matches

Endpoint facts

Method: GET
API path: /vlr/player-matches
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: VLR

VLR.gg VALORANT Esports API Try VLR.gg player match history API in Playground VLR API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

id: required numeric player id from vlr-team or vlr-stats.
page: optional 1-based page, default 1; each page has up to 50 matches.

Notable response behavior:

team is the team the player represented in that match. result is win or loss for that team (upcoming, with an eta, for a match not yet played). The shared response also has a group field (completed or upcoming), which is only set for team histories and is absent here.
has_more is true while older pages exist. An unknown player id returns 404.
The response is cached for up to ten minutes.

Sampled response

Request, 29 Oct 2026: GET /vlr/player-matches?id=9780
Items in matches: 50
Fields filled in every checked item: 9

Field	Filled in, of 50 checked	Values in the sample
id	50
url	50	vlr.gg
event	50	“Champions 2026” and 8 other values
stage	50	“Playoffs ⋅ GF” and 35 other values
team	50	Team Vitality (49), BBL Esports (1)
opponent	50	“LOUD” and 29 other values
score	50	“1:3” and 9 other values
result	50	win (32), loss (18)
date	50	“2026/10/18” and 48 other values

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
id	string	Yes		Numeric VLR player id from vlr-team or vlr-stats	9780
page	integer	No	1	1-based page number; defaults to 1 Minimum: 1. Maximum: 500.

cURL example

curl -X GET "https://api.crawlora.net/api/v1/vlr/player-matches?id=9780&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://www.vlr.gg/player-matches",
    "fetched_at": "2026-10-27T10:00:00Z",
    "id": "9780",
    "page": 1,
    "count": 1,
    "has_more": true,
    "matches": [
      {
        "id": "754737",
        "url": "https://www.vlr.gg/754737/loud-vs-team-vitality-valorant-champions-2026-gf",
        "event": "Champions 2026",
        "stage": "Playoffs ⋅ GF",
        "team": "Team Vitality",
        "opponent": "LOUD",
        "score": "1:3",
        "result": "loss",
        "date": "2026/10/18"
      }
    ]
  }
}

Request schema

No body schema

Response schema

Inline response schema

Field	Type	Required	Enum	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	vlr.HistoryResponse	No
data.count	integer	No		50
data.fetched_at	string	No		2026-10-27T10:00:00Z
data.group	string	No	completed, upcoming	completed
data.has_more	boolean	No		true
data.id	string	No		2059
data.matches	array	No			TeamMatch record, 10 fields: date, eta, event, id, opponent, result, score, stage, team, url. Described under VLR.gg team profile API.
data.page	integer	No		1
data.source_url	string	No		https://www.vlr.gg/matches
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/vlr/player-matches?id=9780&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More VLR endpoint docs VLR.gg VALORANT Esports API VLR.gg event agent pick rates API documentation VLR.gg event matches API documentation VLR.gg event player statistics API documentation VLR.gg event detail API documentation VLR.gg events API documentation VLR.gg forum categories API documentation

Open in Playground Back to group

Docs menu

VLR API endpoint

VLR.gg player match history API

GETapiKey1 credit/requestVLR/vlr/player-matches

Endpoint facts

Method: GET
API path: /vlr/player-matches
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: VLR

VLR.gg VALORANT Esports API Try VLR.gg player match history API in Playground VLR API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

id: required numeric player id from vlr-team or vlr-stats.
page: optional 1-based page, default 1; each page has up to 50 matches.

Notable response behavior:

team is the team the player represented in that match. result is win or loss for that team (upcoming, with an eta, for a match not yet played). The shared response also has a group field (completed or upcoming), which is only set for team histories and is absent here.
has_more is true while older pages exist. An unknown player id returns 404.
The response is cached for up to ten minutes.

Sampled response

Request, 29 Oct 2026: GET /vlr/player-matches?id=9780
Items in matches: 50
Fields filled in every checked item: 9

Field	Filled in, of 50 checked	Values in the sample
id	50
url	50	vlr.gg
event	50	“Champions 2026” and 8 other values
stage	50	“Playoffs ⋅ GF” and 35 other values
team	50	Team Vitality (49), BBL Esports (1)
opponent	50	“LOUD” and 29 other values
score	50	“1:3” and 9 other values
result	50	win (32), loss (18)
date	50	“2026/10/18” and 48 other values

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
id	string	Yes		Numeric VLR player id from vlr-team or vlr-stats	9780
page	integer	No	1	1-based page number; defaults to 1 Minimum: 1. Maximum: 500.

cURL example

curl -X GET "https://api.crawlora.net/api/v1/vlr/player-matches?id=9780&page=1" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://www.vlr.gg/player-matches",
    "fetched_at": "2026-10-27T10:00:00Z",
    "id": "9780",
    "page": 1,
    "count": 1,
    "has_more": true,
    "matches": [
      {
        "id": "754737",
        "url": "https://www.vlr.gg/754737/loud-vs-team-vitality-valorant-champions-2026-gf",
        "event": "Champions 2026",
        "stage": "Playoffs ⋅ GF",
        "team": "Team Vitality",
        "opponent": "LOUD",
        "score": "1:3",
        "result": "loss",
        "date": "2026/10/18"
      }
    ]
  }
}

Request schema

No body schema

Response schema

Inline response schema

Field	Type	Required	Enum	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	vlr.HistoryResponse	No
data.count	integer	No		50
data.fetched_at	string	No		2026-10-27T10:00:00Z
data.group	string	No	completed, upcoming	completed
data.has_more	boolean	No		true
data.id	string	No		2059
data.matches	array	No			TeamMatch record, 10 fields: date, eta, event, id, opponent, result, score, stage, team, url. Described under VLR.gg team profile API.
data.page	integer	No		1
data.source_url	string	No		https://www.vlr.gg/matches
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/vlr/player-matches?id=9780&page=1" \
  -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

VLR.gg player match history API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

VLR.gg player match history API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related