Liquipedia APIliquipedia.net ↗
Access Liquipedia esports data via API: match schedules, team rosters, player profiles, tournament results, and game stats for Valorant, CS, LoL, and Dota 2.
What is the Liquipedia API?
This API exposes 10 endpoints covering esports data from Liquipedia across Valorant, Counter-Strike, League of Legends, and Dota 2. Use get_upcoming_matches to pull live and recent match schedules across all four games, get_cs_esports_data to fetch Counter-Strike player bios, team rosters, and tournament placements in one call, or get_lol_match_player_stats for per-player KDA, CS, gold, and damage figures broken down by game within a series.
curl -X GET 'https://api.parse.bot/scraper/4ee21497-024f-4570-b075-97b9fd21ae78/get_valorant_agent_stats?tournament_path=VCT%2F2025%2FChampions%2FStatistics' \ -H 'X-API-Key: $PARSE_API_KEY'
Extract Valorant agent usage statistics and map play counts from a tournament statistics page on Liquipedia. Returns agent pick rates (when available), individual player stats, and map play counts. The page must use the exact Liquipedia wiki path. Returns stale_input if the tournament page does not exist.
| Param | Type | Description |
|---|---|---|
| tournament_path | string | Tournament statistics page path on the Valorant wiki (e.g. VCT/2025/Champions/Statistics, VCT/2024/Stage_1/Masters/Statistics). Must match the exact Liquipedia page title. |
{
"type": "object",
"fields": {
"map_stats": "array of MapStat objects with map name and total play count",
"tournament": "string - the tournament path used"
},
"sample": {
"data": {
"map_stats": [
{
"Map": "Abyss",
"Total": "15×",
"Playoffs": "5×",
"Group Stage": "10×"
},
{
"Map": "Ascent",
"Total": "16×",
"Playoffs": "9×",
"Group Stage": "7×"
}
],
"tournament": "VCT/2025/Champions/Statistics"
},
"status": "success"
}
}About the Liquipedia API
Match Schedules and Rosters
get_upcoming_matches returns matches from the past hour onward, sorted chronologically, with fields for game, team1, team2, score, start_time_ph (Philippine Time / UTC+8), tournament, and timestamp. It covers Valorant, Counter-Strike, League of Legends, and Dota 2 in a single response. For team-specific roster data on any supported wiki, get_team_roster accepts a team slug and a wiki parameter (leagueoflegends, valorant, counterstrike, dota2) and returns each player's ID, real name, join date, and position where the wiki exposes it.
Counter-Strike and Valorant Data
get_cs_esports_data accepts up to three parameters — player, team, and tournament — in a single call. The player result includes a biographical info map; team includes the active roster array; tournament returns a results array of placement objects. For Valorant, get_valorant_agent_stats takes a tournament_path such as VCT/2025/Champions/Statistics and returns map_stats (map name and total play count) alongside agent pick rates and individual player stats where the tournament page includes them.
League of Legends Match Detail
get_lol_team_matches accepts a team slug plus optional start_date and end_date filters and returns individual game rows with champion picks and bans for both sides, result, opponent, game length, patch, and a match_id. That match_id feeds directly into get_lol_match_player_stats (10 players per game, with kills, deaths, assists, CS, gold, and damage) and get_lol_match_objectives (towers, inhibitors, barons, dragons, heralds, void grubs, total kills, and total gold per team). get_lol_teams can enumerate all teams on the LoL Portal, filterable by start_year and end_year, returning team_name, team_slug, region, and active_years.
Dota 2 Hero and Item Reference
get_dota2_hero looks up a hero by name and returns the full abilities array (each with ability_type, affects, damage_type, description, and stats), the talents tree (levels 10/15/20/25 with left and right choices), and aghanims upgrade descriptions for both Scepter and Shard. get_dota2_item returns cost, sell_value, recipe_cost, bonuses, components, and a full ability object covering the item's active or passive effect.
The Liquipedia API is a managed, monitored endpoint for liquipedia.net — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when liquipedia.net changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official liquipedia.net API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display a live esports match ticker using get_upcoming_matches fields for team names, scores, and tournament
- Build a CS2 player profile page pulling biographical data from get_cs_esports_data with the player parameter
- Analyze LoL champion meta by aggregating picks and bans from get_lol_team_matches across a date range
- Compare per-player damage and gold output across games in a series using get_lol_match_player_stats
- Track VCT map pool trends by parsing map_stats from get_valorant_agent_stats across multiple tournaments
- Populate a Dota 2 reference tool with hero abilities, talent trees, and Aghanim's upgrades from get_dota2_hero
- Enumerate all LoL teams active in a specific year range using get_lol_teams with start_year and end_year filters
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.