Dota2ProTracker APIdota2protracker.com ↗
Access high-MMR Dota 2 hero winrates, ELO ratings by position, recent match details with facets and items, and player/hero search via the Dota2ProTracker API.
What is the Dota2ProTracker API?
The Dota2ProTracker API exposes 3 endpoints covering high-MMR Dota 2 meta data: hero ELO ratings and winrates broken down across all 5 positions, recent matches with per-player facet selections and item builds, and a combined hero/player search. The get_heroes endpoint alone returns per-position elo, match count, and winrate for every hero in the current pool, giving a direct read on the current competitive meta.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/66214c1a-6b6f-423b-9d88-1a64261b7b38/get_heroes' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace dota2protracker-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Dota2ProTracker SDK — bounded, re-runnable; every call capped."""
from parse_apis.Dota2ProTracker_API import Dota2ProTracker, InvalidDaysRange
client = Dota2ProTracker()
# List top heroes with per-position stats.
for hero in client.heros.list(limit=5):
print(hero.display_name, hero.all_elo, hero.all_winrate)
# Fetch recent high MMR matches from the last 30 days.
match = client.matches.list(days=30, limit=1).first()
if match:
print(match.match_id, match.mmr, match.duration, match.radiant_score, match.dire_score)
for player in match.players[:3]:
print(player.hero_name, player.kills, player.deaths, player.assists, player.net_worth)
# Search for players by name keyword.
results = client.search_results.find(query="invoker")
for player in results.players[:3]:
print(player.name, player.matches, player.wins)
# Typed error handling: catch invalid days parameter.
try:
for m in client.matches.list(days=0, limit=1):
print(m.match_id)
except InvalidDaysRange as exc:
print(f"Invalid input: {exc}")
print("exercised: heros.list / matches.list / search_results.find / InvalidDaysRange")
Retrieves the full roster of Dota 2 heroes with ELO ratings, winrates, and match counts broken down by position (1-5) and aggregate. Returns all heroes in a single response with no filtering — client-side filtering is required for position or attribute analysis. Each hero includes per-position statistics so callers can identify position-specific meta trends.
No input parameters required.
{
"type": "object",
"fields": {
"heroes": "array of hero objects each containing displayName, hero_id, primary_attribute, npc, and per-position elo/matches/winrate stats"
}
}About the Dota2ProTracker API
Hero Stats and ELO Ratings
The get_heroes endpoint returns the full hero roster with no required parameters. Each hero object includes displayName, hero_id, primary_attribute, and per-position breakdowns (positions 1–5) each containing an ELO score, total match count, and winrate. An aggregate entry across all positions is also included. This makes it straightforward to compare how a hero performs specifically as a carry versus a support without filtering client-side.
High-MMR Match Data
The get_matches endpoint returns recent matches sorted by activate_time descending. You can narrow results using the days parameter (1–30), control result size with limit, and paginate with offset. Each match object includes match_id, mmr, duration, radiant_win, radiant_score, dire_score, and a players array. Player entries carry facet selections, item builds, and networth timelines, making this endpoint useful for tracking how specific hero-facet combinations perform in elite-bracket play.
Hero and Player Search
The search endpoint accepts an optional query string and always returns the full hero roster alongside a filtered player list. Hero objects include displayName, npc, and hero_id. Player objects include account_id and matching name fields. Omitting the query returns all heroes and a default player set, which is useful for bootstrapping a local hero index or autocomplete list.
The Dota2ProTracker API is a managed, monitored endpoint for dota2protracker.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when dota2protracker.com 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 dota2protracker.com 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?+
- Build a draft assistant that ranks heroes by per-position winrate and ELO from
get_heroes. - Track meta shifts over time by polling
get_heroesdaily and storing winrate deltas per hero. - Analyze which hero facets appear most in high-MMR matches using the
playersarray fromget_matches. - Compare item builds for a specific hero across recent elite-bracket matches via
get_matchesplayer data. - Implement an autocomplete search for heroes and professional players using the
searchendpoint. - Build a networth-timeline visualizer using per-player timeline data from
get_matches. - Filter recent matches by MMR tier using the
daysandlimitparameters to study short-term meta trends.
| 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 | 100 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 Dota2ProTracker have an official developer API?+
What does the `get_matches` endpoint include for each player in a match?+
players array includes their facet selection, item build, and networth timeline for that match, alongside hero and team information. The endpoint is scoped to high-MMR games and sorted by activation time descending; you can use days (1–30), limit, and offset to control the result window.Does `get_heroes` return hero data for a specific patch or time window?+
Can I look up a specific player's full match history?+
search endpoint returns player records matched by name, and get_matches includes player data within match results. A dedicated player-profile endpoint with full personal match history is not currently part of this API. You can fork it on Parse and revise to add a player-specific match history endpoint.How does pagination work for `get_matches`?+
offset integer parameter alongside limit to page through results. Results are always sorted by activate_time descending, so incrementing offset by your limit value steps through older matches. The days parameter (1–30) sets the outer time boundary for the query.