Tracker APItracker.gg ↗
Access Valorant player profiles, match history, leaderboards, agent insights, and reference data from tracker.gg via 8 structured endpoints.
What is the Tracker API?
This API exposes 8 endpoints covering Valorant player data from tracker.gg, including player profiles, per-segment statistics, match history, and competitive leaderboards. The get_player_segments endpoint breaks down performance by agent, map, weapon, or season — returning fields like kDRatio, matchesWinPct, and headshots for any act. get_match_rounds delivers round-by-round spike plant and defuse events for a single match UUID.
curl -X GET 'https://api.parse.bot/scraper/6517942a-644e-4cbc-9349-6e6d5ddaa622/get_player_profile?player_id=TenZ%2300000' \ -H 'X-API-Key: $PARSE_API_KEY'
Get general player information and overview stats including platform info, user info, metadata, and season segments. Requires the exact Riot ID with correct casing and tag number. Returns platform details, user account info, privacy/season/playlist metadata, and stat segments for the player's default season.
| Param | Type | Description |
|---|---|---|
| player_idrequired | string | Player Riot ID in Name#Tag format (e.g., 'TenZ#00000'). Must use exact casing and tag number as registered on Riot. |
{
"type": "object",
"fields": {
"metadata": "object containing activeShard, schema, privacy, defaultPlatform, defaultPlaylist, accountLevel, seasons list, playlists",
"segments": "array of stat segments (season overview with detailed combat/game stats)",
"userInfo": "object containing user account info (isPremium, isVerified, pageviews, socialAccounts)",
"platformInfo": "object containing platform details (platformSlug, platformUserId, platformUserHandle, avatarUrl)"
}
}About the Tracker API
Player Profiles and Segment Stats
The get_player_profile endpoint accepts a Riot ID in Name#Tag format — casing and tag number must match exactly as registered — and returns platformInfo (avatar URL, platform handle), userInfo (premium/verified status, page views), and a metadata object listing available seasons, playlists, and the account level. The get_player_segments endpoint extends this with per-segment breakdowns: pass a segment_type of agent, map, weapon, or season, and optionally a season_id UUID from get_reference_data, to receive per-entry stats including kDRatio, matchesPlayed, matchesWinPct, and headshots.
Match History and Round Detail
get_player_matches returns a player's recent competitive matches, each object carrying map name, mode, result, timestamp, agent, and per-player stat segments covering kills, deaths, damage, and performance score. Match UUIDs in matches[*].attributes.id feed directly into get_match_rounds, which returns the full round timeline for a single match: a rounds array ordered by round number with plant and defuse objects (player ID, site, round time in ms, x/y location), winning_team, and the result per round. Header fields include total_rounds, season_id, map_name, and an ISO-8601 date_started.
Leaderboards and Agent Insights
get_leaderboard retrieves ranked leaderboard entries for a given region (na, eu, ap, kr, br, latam) and optional act_id, returning each player's rank, ranked rating value, top agents, and avatar. Up to 100 entries are returned per call. get_agent_insights aggregates global agent performance for the current or a specified act, providing pickRate, wlPercentage, kdRatio, and daily usage histograms per agent, plus the active patchVersion.
Reference Data
get_reference_data accepts a data_type of agents, seasons, maps, weapons, or playlists and returns UUID-keyed arrays. Agent entries include role, abilities, slug, and image URL. Season entries are grouped by episode with date ranges — the UUID values here are the season_id and act_id params accepted by other endpoints. get_games_on_date filters a player's match history to a specific YYYY-MM-DD date and returns a count plus the matching match objects.
The Tracker API is a managed, monitored endpoint for tracker.gg — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when tracker.gg 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 tracker.gg 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?+
- Track a Valorant player's K/D ratio and win rate progression across multiple acts using get_player_segments with historical season_id values.
- Build a round-replay tool by extracting spike plant locations (x/y coordinates) and defuse events from get_match_rounds for a given match UUID.
- Generate regional leaderboard snapshots for esports coverage using get_leaderboard with region and act_id parameters.
- Monitor agent meta shifts over time by polling get_agent_insights across acts for pickRate and wlPercentage trends.
- Identify how many games a player logged on a specific date using get_games_on_date for activity tracking or challenge verification.
- Populate a weapon or map performance dashboard using get_player_segments with segment_type set to weapon or map.
- Resolve all current agent UUIDs, abilities, and roles for a game database via get_reference_data with data_type=agents.
| 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.
Does tracker.gg have an official developer API?+
What does get_match_rounds return beyond win/loss per round?+
rounds array ordered by round number. Each entry includes the result, winning_team, and — when applicable — a plant object with the planting player's ID, site, time in milliseconds, and x/y map coordinates, plus a matching defuse object. It also surfaces match-level fields: map_name, mode_name, total_rounds, date_started, and the season_id UUID that links back to get_player_segments.Does the API return match history beyond the most recent matches?+
get_player_matches and get_games_on_date endpoints are limited to the most recent matches available for a player — there is no pagination parameter to retrieve older pages. The API covers current and recent match history. You can fork it on Parse and revise to add deeper historical pagination if the source supports additional pages.Does the API cover game modes other than competitive, like Premier or Deathmatch?+
get_leaderboard endpoint focuses on ranked (competitive) data, and get_player_matches returns competitive match history by default. Non-competitive modes such as Premier, Spike Rush, or Deathmatch are not currently surfaced as dedicated endpoints. You can fork it on Parse and revise to add endpoints targeting those modes.Can I look up a player by display name alone without knowing the tag number?+
Name#Tag format with correct casing and the exact numeric tag. There is no search or autocomplete endpoint that resolves partial names or unknown tags. You can fork it on Parse and revise to add a name-search endpoint if that lookup becomes available.