VALORANT match and event monitoring
VLR.ggエンドポイントを使えば、「VALORANT match and event monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
翻訳作業中です。 日本語訳を準備中のため、このページは一時的に英語で表示されます。
スポーツ＆ゲーム稼働中エンドポイント 23件apiKey
VLR.gg VALORANT Esports API
Join VLR.gg's search, event, match, team, and player records into VALORANT research, while keeping search windows and round-level availability explicit.
Collect VLR.gg VALORANT search, schedules, events, results, rankings, player statistics, and match-level performance data.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
78
サンプル数
23
ライブカタログスナップショット
VLR.ggのカバレッジ
稼働エンドポイント
23
メソッド
GET
必須パラメータ
38
スキーマ参照
23
Event1
Event Agents1
Event Matches1
Event Stats1
{
"platform": "VLR.gg",
"endpoint": "vlr-event",
"method": "GET",
"path": "/vlr/event",
"auth": "apiKey"
}ユースケース
VLR.ggに適したワークフロー
Collect VLR.gg VALORANT search, schedules, events, results, rankings, player statistics, and match-level performance data.
Regional team ranking research
VLR.ggエンドポイントを使えば、「Regional team ranking research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Player and map statistics
VLR.ggエンドポイントを使えば、「Player and map statistics」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
Crawloraによるこのプラットフォームの処理方法
以下の数値はすべて、稼働中のVLR.ggエンドポイントカタログから取得しています（エンドポイント23件、ドキュメント化されたリクエストパラメータ78個、公開レスポンススキーマ23件）。DocsとPlaygroundが参照しているカタログと同じものです。
ドキュメント化されたエンドポイント
VLR.ggのエンドポイントは23件、23つのリクエストファミリーに分類されています（Event、Event Agents、Event Matchesほか20件）。
公開されたリクエスト仕様
これらのVLR.ggエンドポイントには78個のリクエストパラメータがドキュメント化されており、うち38個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
判明しているレスポンス構造
23件のVLR.ggエンドポイントのうち23件が実際のサンプルレスポンスを、23件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
ドキュメント化されたエラー
VLR.ggのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
エージェントから呼べるMCPツール
VLR.ggのエンドポイントは23個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
統合前にAPIで収集できるデータを把握
1エンドポイント
Event
/vlr/event
GETapiKey
1エンドポイント
Event Agents
/vlr/event-agents
GETapiKey
1エンドポイント
Event Matches
/vlr/event-matches
GETapiKey
1エンドポイント
Event Stats
/vlr/event-stats
GETapiKey
1エンドポイント
Events
/vlr/events
GETapiKey
1エンドポイント
Forum Categories
/vlr/forum-categories
GETapiKey
主要エンドポイント
VLR.gg APIエンドポイント
GETapiKeyexample
/vlr/eventVLR.gg Valorant event detail and participating teams
Returns one VLR.gg event: name, series, dates, prize, location and the participating teams with ids. Use vlr-event-matches for its matches and vlr-team for a team.
レスポンスに関する注記
- `teams` lists the teams registered for the event with their ids; an event whose bracket is not set yet can return an empty list. - An unknown event id returns `404`. The response is cached for up to ten minutes.
MCPツール vlr_event
x-api-key:headerid:query
GETapiKeyexample
/vlr/event-agentsVLR.gg Valorant event agent pick rates by map
Returns the agent pick-rate matrix of one VLR.gg event: for the whole event and for each map, the number of games, the attack-side and defense-side round win rates and the share of games in which each agent was played. Also returns, per map, each team's agents used and the agents picked in each of its matches (compositions). Use it to see an event's meta; vlr-stats gives per-player agent usage.
レスポンスに関する注記
- `overall` covers all maps; `maps[]` has one row per map played. `pick_rates[].percent` is the share of that map's games in which a team played the agent (0 to 100); `agents` lists the columns in the site's order. - `attack_win_percent` and `defense_win_percent` are round win rates by side. An unknown event id returns `404`; an event with no played maps has no rows. - The response is cached for up to ten minutes. - `compositions[]` lists, per map, each team's `agents_used` and its `matches` with the five `agents` picked and the `result`, which has these values: `win`, `loss`.
MCPツール vlr_event_agents
x-api-key:headerid:query
GETapiKeyexample
/vlr/event-matchesVLR.gg Valorant event match list
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.
レスポンスに関する注記
- `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](vlr-matches.md); `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`.
MCPツール vlr_event_matches
x-api-key:headerid:queryseries_id:query他1件
GETapiKeyexample
/vlr/event-statsVLR.gg Valorant event player statistics
Returns the player statistics table of one VLR.gg event (rating, ACS, K:D, KAST, ADR, per-round rates, first kills, clutches, totals) for every player who appeared, optionally for one `side` (`all`, `t` attack, `ct` defend). For league-wide filtered statistics use vlr-stats.
レスポンスに関する注記
- Rows use the same fields as [vlr-stats](vlr-stats.md). Fields VLR does not publish for an event are omitted. - The whole table is returned in one response. An unknown event id returns `404`; an event with no played maps yet returns an empty list. - The response is cached for up to ten minutes.
MCPツール vlr_event_stats
x-api-key:headerid:queryside:query他7件
GETapiKeyexample
/vlr/eventsVLR.gg Valorant events
Returns Valorant events from VLR.gg: ongoing, upcoming and completed events with prize pool, dates and region flag. Filter by `tier` (`all`, `vct`, `vcl`, `t3`, `gc`, `cg`, `off`) and `region` (`all`, `americas`, `emea`, `pacific`, `china`); `page` pages through completed events. Use vlr-event with a returned `id`.
レスポンスに関する注記
- `status` has these values: `upcoming`, `ongoing`, `completed`. `prize` and `dates` are the site's display strings. - `has_more` is true while further pages exist. - The response is cached for up to ten minutes.
MCPツール vlr_events
x-api-key:headertier:queryregion:query他1件
GETapiKeyexample
/vlr/forum-categoriesVLR.gg forum categories
Returns the VLR.gg forum directory: each category with slug, name, group, description, thread and post counts and the last poster, time and thread. `slug` is one of `valorant-discussion`, `off-topic`, `site-feedback`; use it as `category` in vlr-forum-threads.
レスポンスに関する注記
- `slug` has these values: `valorant-discussion`, `off-topic`, `site-feedback`. `group` is the heading the category is listed under on the site. - `threads` and `posts` are the category totals; `last_post_time` is the site's exact timestamp string. - The response is cached for up to ten minutes.
MCPツール vlr_forum_categories
x-api-key:header
関連API
スポーツ＆ゲームのその他のカバレッジ
Sports & Gaming
FanDuel Sportsbook
Browse public sports and event data from FanDuel Sportsbook. Discover market-specific event types, follow a league or schedule, and read the markets and prices FanDuel publishes for that event and market.
Sports & Gaming
FanDuel Racing
Follow public horse-racing cards across tracks and countries. Discover today's tracks, inspect races and runners, and read official results, wager-type reference data, and published pool information without placing a wager.
Sports & Gaming
FanDuel Research
Explore FanDuel Research's public editorial and sports-data surfaces. Discover sport slugs and teams, read articles and player updates, inspect live fixtures, and retrieve the published projection tables with their source-specific slate identifiers.
VLR.ggのスクレイピング方法
7ステップでVLR.ggのデータを抽出
VLR.gg is a dedicated VALORANT esports publisher whose current site separates ongoing, upcoming, and completed events and carries schedules, results, news, rankings, and match statistics. The event mix includes VCT and Game Changers; match detail can add maps, economy, player performance, agent picks, and round logs when VLR publishes those records. Crawlora mirrors that linked data model: discover an event or ranking, reuse returned team/player/match IDs, then request the corresponding detail. Match and result lists use 50-row pages. Their displayed time label is not guaranteed to have a timezone, so use match detail's `start_time_utc` for normalized analysis. The news list carries writer names, and the ID-based news-article route returns article text; it does not provide author profiles or byline search. Round logs exist only when a replay is available, and player stats may be incomplete while a match is processed. On 2026-10-30 the first events page returned 91 events mixing ongoing, upcoming and completed records, the results page returned 50 rows with the newest dated 2026-10-29, and the North America ranking listed 197 teams led by 100 Thieves (rating 2000, record 62–35).
- ステップ 1
Discover events before opening their records
/vlr/events accepts tier, region, and a 1-based page; the event ID returned there links to event detail, event matches, event stats, and event agent rates. Preserve the requested filters because an event list is a snapshot of VLR's changing calendar. Dates and prizes are display strings, not typed values: on 2026-10-30 Game Changers 2026: Championship São Paulo read "Oct 22—Nov 3" with "$500,000", VCT 2026: China Threshold read "Oct 21—Nov 1" with "TBD", and a Kaizen league read "Sep 12—TBD". Keep the raw text and parse it separately.
- ステップ 2
Search source records, then follow their IDs
/vlr/search accepts q (1 to 100 characters) and optional type all, teams, events, or players. A short query can return roughly 190 mixed results on a single page, with no pagination; use type to narrow it. Follow each result's kind and ID to /vlr/team, /vlr/event, or /vlr/player rather than treating a search record as a complete profile.
- ステップ 3
Page match schedules and results
/vlr/matches and /vlr/results accept page numbers and return up to 50 records per page with has_more. The schedule groups cards by day; time_label reflects site display text, not a guaranteed timezone. Use /vlr/match's start_time_utc when you need normalized timing. The two newest results on 2026-10-30 were China Threshold quarterfinals, World Sports Invictus Gaming 2–1 over Titan Esports Club (match 777961, label "8:00 AM", eta "16h 0m") and Unsettled Resentment 2–1 over KeepBest Gaming (777960); both listed stats but no VODs, so has_vods can flip later. Subtracting the eta from the 03:59 UTC fetch puts the first at roughly 12:00 UTC, which the label alone does not say.
- ステップ 4
Open news text by returned article ID
/vlr/news returns paged headlines with a writer name. Pass an item's numeric ID to /vlr/news-article to get its body paragraphs, references to teams/players/events, published_at, and external links. The byline is metadata; there is no author-profile or arbitrary byline-search route. The first page on 2026-10-30 held 30 items dated 2026-10-22 to 2026-10-29, mostly offseason roster moves such as free-agency notices, after the Valorant Champions 2026 grand final on 2026-10-18 (match 754737, LOUD 3–1 Team Vitality).
- ステップ 5
Pick a ranking region before comparing teams
/vlr/rankings takes a region (north-america by default, plus europe, brazil, asia-pacific, korea, china, japan, la-s, la-n, oceania, mena, gc or collegiate) and a limit from 1 to 250, default 50. Regions are separate tables with their own totals, so a rating in one is not comparable with another. Earnings arrive as text such as "$2,635,500" for NRG, and the streak is a label like "2L" or "8W".
- ステップ 6
Carry IDs through team and player analysis
Use IDs from rankings, event, or match responses for team detail and team maps; use player IDs from team rosters or filtered stats for player detail and player matches. A detail ID copied from another site or region may return 404.
- ステップ 7
Read optional statistics as source availability
The event and match detail family adds map, economy, agent, advanced performance, and round-by-round fields. Some stats appear only after VLR processes a match; match-rounds is available only when a replay is published. An empty unavailable block is not a zero-performance result.
FAQ
VLR.ggのスクレイピング：よくある質問
Are match schedule times normalized to UTC?
No. The match list includes VLR's displayed time label, whose timezone is not guaranteed. Use the match detail route's start_time_utc for normalized timestamps.
How does VLR search differ from its detail endpoints?
/vlr/search finds teams, events, and players by a 1–100 character q value; optional type filters the group. It returns one unpaged list, so pass a result's kind and ID to the matching team, event, or player endpoint for details.
Why is a match-rounds response unavailable?
VLR publishes round logs only for matches with an available replay. The API reports unavailable explicitly; it does not infer missing rounds or map positions.
Does VLR provide article text or author profiles?
Yes to article text: pass an ID from the paged `/vlr/news` list to `/vlr/news-article` for the story text and references. There is no author-profile or arbitrary byline-search route.
Are VLR dates and prize pools numbers?
No. Event dates are year-less text ranges and prizes are display strings, including "TBD" and "$0" on 2026-10-30. Store the original text, then derive a numeric amount or date range yourself and treat TBD as unknown rather than zero.
Can I filter VLR player stats?
Yes. The stats route documents filters for tier, region, timespan, side, role, agent, map, minimum rounds and rating, sort direction, and page. Use its allowed values; they are not interchangeable with event or team IDs.