Docs menu

VLR API endpoint

VLR.gg event matches API

Returns every match of one VLR.gg event (upcoming, live and completed) with teams, scores, stage and whether stats or VODs exist. Use vlr-match with a returned `id` for map detail.

GETapiKey1 credit/requestVLR/vlr/event-matches

Endpoint facts

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

VLR.gg VALORANT Esports API Try VLR.gg event matches API in Playground VLR API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

id: required numeric event id from vlr-events.
series_id: optional numeric stage id (a week, group or bracket round) taken from the stages list of an earlier response; omit it for every stage.
group: optional; allowed values: completed, upcoming. Omit it for both.

Notable response behavior:

stages lists the event's stage selector (id, name) on every response, including the stage you filtered on; series_id and group are echoed when sent.
Matches use the same shape as vlr-matches; series is the stage and event the week or bracket label.
An unknown event id returns 404. The response is cached for up to five minutes.
status has these values: upcoming, live, completed.

Sampled response

Request, 29 Oct 2026: GET /vlr/event-matches?id=3166
Items in matches: 22
Fields filled in every checked item: 11

Field	Filled in, of 22 checked	Values in the sample
id	22
url	22	vlr.gg
date	22	2026-10-21 to 2026-11-01
time_label	22	“12:00 AM” and 9 other values
status	22	completed (17), upcoming (5)
eta	22	“1w 1d” and 17 other values
teams	22	median 2 entries
event	22	Week 1 (11), Week 2 (11)
series	22	Round of 12 (8), Quarterfinals (8), Semifinals (4) and 1 more
has_stats	22	true in 17 of 22
has_vods	22	true in 15 of 22

Request parameters

Parameter	Type	Required	Description	Example
x-api-key (header)	string	Yes	API key required
id	string	Yes	Numeric VLR event id from vlr-events	3166
series_id	string	No	Stage id from the stages list of an earlier response (a week, group or bracket round); omit for every stage	6080
group	string	No	Match group; one of completed, upcoming; omit for both Allowed values: completed, upcoming.

cURL example

curl -X GET "https://api.crawlora.net/api/v1/vlr/event-matches?id=3166&group=completed" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://www.vlr.gg/event-matches",
    "fetched_at": "2026-10-27T10:00:00Z",
    "event_id": "3166",
    "count": 1,
    "matches": [
      {
        "id": "777944",
        "url": "https://www.vlr.gg/777944/wolves-esports-vs-a-team-vct-china-2026-threshold-week-1-ro12",
        "date": "2026-10-21",
        "status": "completed",
        "teams": [
          {
            "name": "Wolves Esports",
            "score": 2,
            "winner": true
          },
          {
            "name": "A Team",
            "score": 0,
            "winner": false
          }
        ],
        "event": "Week 1",
        "series": "Round of 12",
        "has_stats": true,
        "has_vods": true
      }
    ]
  }
}

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.EventMatchesResponse	No
data.count	integer	No		22
data.event_id	string	No		3166
data.fetched_at	string	No		2026-10-27T10:00:00Z
data.group	string	No	completed, upcoming	completed
data.matches	array	No			MatchSummary record, 16 fields: date, eta, event, has_stats, has_vods, id, note, series, status, teams, time_label, url. Described under VLR.gg upcoming and live matches API.
data.series_id	string	No		6080
data.source_url	string	No		https://www.vlr.gg/matches
data.stages	array	No
data.stages[].id	string	No		6080
data.stages[].name	string	No		Week 1
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/event-matches?id=3166&group=completed" \
  -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 player statistics API documentation VLR.gg event detail API documentation VLR.gg events API documentation VLR.gg forum categories API documentation VLR.gg forum threads API documentation

Open in Playground Back to group

Docs menu

VLR API endpoint

VLR.gg event matches API

Returns every match of one VLR.gg event (upcoming, live and completed) with teams, scores, stage and whether stats or VODs exist. Use vlr-match with a returned `id` for map detail.

GETapiKey1 credit/requestVLR/vlr/event-matches

Endpoint facts

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

VLR.gg VALORANT Esports API Try VLR.gg event matches API in Playground VLR API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

id: required numeric event id from vlr-events.
series_id: optional numeric stage id (a week, group or bracket round) taken from the stages list of an earlier response; omit it for every stage.
group: optional; allowed values: completed, upcoming. Omit it for both.

Notable response behavior:

stages lists the event's stage selector (id, name) on every response, including the stage you filtered on; series_id and group are echoed when sent.
Matches use the same shape as vlr-matches; series is the stage and event the week or bracket label.
An unknown event id returns 404. The response is cached for up to five minutes.
status has these values: upcoming, live, completed.

Sampled response

Request, 29 Oct 2026: GET /vlr/event-matches?id=3166
Items in matches: 22
Fields filled in every checked item: 11

Field	Filled in, of 22 checked	Values in the sample
id	22
url	22	vlr.gg
date	22	2026-10-21 to 2026-11-01
time_label	22	“12:00 AM” and 9 other values
status	22	completed (17), upcoming (5)
eta	22	“1w 1d” and 17 other values
teams	22	median 2 entries
event	22	Week 1 (11), Week 2 (11)
series	22	Round of 12 (8), Quarterfinals (8), Semifinals (4) and 1 more
has_stats	22	true in 17 of 22
has_vods	22	true in 15 of 22

Request parameters

Parameter	Type	Required	Description	Example
x-api-key (header)	string	Yes	API key required
id	string	Yes	Numeric VLR event id from vlr-events	3166
series_id	string	No	Stage id from the stages list of an earlier response (a week, group or bracket round); omit for every stage	6080
group	string	No	Match group; one of completed, upcoming; omit for both Allowed values: completed, upcoming.

cURL example

curl -X GET "https://api.crawlora.net/api/v1/vlr/event-matches?id=3166&group=completed" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://www.vlr.gg/event-matches",
    "fetched_at": "2026-10-27T10:00:00Z",
    "event_id": "3166",
    "count": 1,
    "matches": [
      {
        "id": "777944",
        "url": "https://www.vlr.gg/777944/wolves-esports-vs-a-team-vct-china-2026-threshold-week-1-ro12",
        "date": "2026-10-21",
        "status": "completed",
        "teams": [
          {
            "name": "Wolves Esports",
            "score": 2,
            "winner": true
          },
          {
            "name": "A Team",
            "score": 0,
            "winner": false
          }
        ],
        "event": "Week 1",
        "series": "Round of 12",
        "has_stats": true,
        "has_vods": true
      }
    ]
  }
}

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.EventMatchesResponse	No
data.count	integer	No		22
data.event_id	string	No		3166
data.fetched_at	string	No		2026-10-27T10:00:00Z
data.group	string	No	completed, upcoming	completed
data.matches	array	No			MatchSummary record, 16 fields: date, eta, event, has_stats, has_vods, id, note, series, status, teams, time_label, url. Described under VLR.gg upcoming and live matches API.
data.series_id	string	No		6080
data.source_url	string	No		https://www.vlr.gg/matches
data.stages	array	No
data.stages[].id	string	No		6080
data.stages[].name	string	No		Week 1
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/event-matches?id=3166&group=completed" \
  -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 event matches 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 event matches API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related