liquipedia.net APIliquipedia.net ↗
Access Liquipedia esports data via API: match schedules, team rosters, player profiles, tournament results, and Valorant agent stats across CS, LoL, and Dota 2.
curl -X GET 'https://api.parse.bot/scraper/4ee21497-024f-4570-b075-97b9fd21ae78/get_valorant_agent_stats?tournament_path=VCT%2F2024%2FChampions%2FStatistics' \ -H 'X-API-Key: $PARSE_API_KEY'
Extract Valorant agent usage statistics and player performance data from a tournament statistics page on Liquipedia. Returns agent pick rates, individual player stats, and map play counts. Returns stale_input if the tournament page does not exist.
| Param | Type | Description |
|---|---|---|
| tournament_path | string | Tournament statistics page path on the Valorant wiki. Must match the exact Liquipedia page title. |
{
"type": "object",
"fields": {
"data": "object containing agent_stats (array of {agent, players_using, usage_rate}), player_stats (array of player performance objects), total_players (integer), and map_stats (array of map play count objects)",
"tournament": "string - the tournament path used"
},
"sample": {
"data": {
"data": {
"map_stats": [
{
"Map": "Abyss",
"Total": "14×",
"Group A": "2×",
"Group B": "4×",
"Group C": "0×",
"Group D": "0×",
"Playoffs": "8×"
}
],
"agent_stats": [
{
"agent": "Viper",
"usage_rate": 35,
"players_using": 28
},
{
"agent": "Omen",
"usage_rate": 27.5,
"players_using": 22
}
],
"player_stats": [
{
"#": "1",
"A": "54",
"D": "202",
"K": "269",
"KD": "1.33",
"ACS": "258",
"ADR": "181",
"KDA": "1.60",
"KAST": "74.7%",
"Maps": "14",
"Team": "",
"A/Map": "3.9",
"D/Map": "14.4",
"FK/FD": "51 / 42",
"K/Map": "19.2",
"Agents": [
"Raze",
"Yoru"
],
"Player": "Derke"
}
],
"total_players": 80
},
"tournament": "VCT/2024/Champions/Statistics"
},
"status": "success"
}
}About the liquipedia.net API
The Liquipedia API exposes esports data across 4 endpoints covering Valorant, Counter-Strike, League of Legends, and Dota 2. Use get_upcoming_matches to pull live and recent match schedules with scores and start times, get_team_roster to retrieve active rosters from any supported wiki, or get_valorant_agent_stats for per-tournament agent pick rates and player performance figures. Counter-Strike player bios, team rosters, and tournament placements are all available through get_cs_esports_data.
Match Schedules and Roster Data
get_upcoming_matches returns a chronological array of match objects, each with game, team1, team2, score, and start_time_ph fields. Coverage spans Valorant, Counter-Strike, League of Legends, and Dota 2, with results starting from the last hour. No filtering parameters are accepted — all four games are returned in a single call.
get_team_roster accepts a team page name and a wiki slug (leagueoflegends, valorant, counterstrike, or dota2). The response includes each player's ID, Name, and Join Date. Some wikis also return a Position field; others do not. If the team page does not exist on Liquipedia, the endpoint returns a stale_input error rather than an empty array.
Counter-Strike and Valorant Specifics
get_cs_esports_data accepts up to three independent parameters — team, player, and tournament — and returns whichever objects correspond to the params you provide. A team response includes the roster as an array of {ID, Name, Join Date} objects. A player response includes a name string and an info object with biographical key-value pairs drawn from the Liquipedia infobox (nationality, birth date, team history, etc.). A tournament response includes placement results. At least one parameter is required.
get_valorant_agent_stats targets a specific tournament statistics page via the tournament_path parameter, which must match the exact Liquipedia page title. The data object contains agent_stats — an array of {agent, players_using, usage_rate} objects — alongside player_stats with individual performance figures and map play counts for the tournament. If the page does not exist, the endpoint returns stale_input.
- Display live match countdowns by polling
get_upcoming_matchesfor start times across all four supported games - Build a CS2 team tracker that shows current roster members and join dates using
get_cs_esports_datawith theteamparam - Pull player biographies for fantasy esports apps via the
playerparam inget_cs_esports_data - Analyze Valorant agent meta trends by comparing
usage_ratevalues across multiple tournaments withget_valorant_agent_stats - Track tournament standings and placement results for Counter-Strike events using
get_cs_esports_datawith thetournamentparam - Sync multi-game roster pages by querying
get_team_rosterwith the appropriatewikislug for each title - Identify which agents specific players favor by cross-referencing
player_statsfromget_valorant_agent_stats
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Liquipedia have an official developer API?+
What does `get_cs_esports_data` return when I pass all three parameters at once?+
team (with roster), player (with infobox fields), and tournament (with placement results) — in a single response. Each object is only present when its corresponding parameter is supplied. You can pass one, two, or all three in a single request.How specific does `tournament_path` need to be for `get_valorant_agent_stats`?+
stale_input rather than partial data.Does the API cover game titles beyond Valorant, Counter-Strike, League of Legends, and Dota 2?+
get_team_roster accepts only the wiki slugs leagueoflegends, valorant, counterstrike, and dota2. Liquipedia hosts wikis for many other games (Rocket League, PUBG, StarCraft, etc.) that are not covered here. You can fork this API on Parse and revise it to add endpoints targeting those additional wikis.Is historical match data available through `get_upcoming_matches`?+
get_cs_esports_data with a tournament param for historical placement results in Counter-Strike. You can fork the API on Parse and revise it to add a dedicated historical match history endpoint for other games.