OpenDota
Connect OpenDota to the rest of your business, with the right person approving what changes and a record of every action.
24 ways to read.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with OpenDota, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- List recent pro matches for a heroRead
Example flow
- OpenDota · List recent pro matches for a heroDone
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches OpenDota.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to OpenDota
- OpenDota's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Public Dota 2 data from OpenDota: heroes and hero stats, matches, pro and public match feeds, players, teams and leagues; read-only, no wagering.
OpenDota API docs- Source actions
- 24
- Data types
- 21
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Hero item popularity1
- Get hero item popularitySource
Read item purchase counts by game phase for a hero.
Hero matches1
- List recent pro matches for a heroSource
Read recent professional matches featuring a hero.
Hero matchups1
- List hero matchupsSource
Read games played and wins for a hero against each opposing hero.
Hero stats1
- List hero statsSource
Read hero attributes and recent pick and win counts by bracket.
Heroes1
- List Dota 2 heroesSource
Read public game reference data.
League matches1
- List league matchesSource
Read matches played in a league.
Leagues2
- Get leagueSource
Read one league.
- List leaguesSource
Read Dota 2 leagues and tiers.
Matches1
- Get matchSource
Read a match summary with per-player results.
Player heroes1
- List player hero performanceSource
Read games and wins per hero for a player.
Player matches1
- List player matchesSource
Read a player's matches, newest first, with optional filters.
Player rankings1
- List player hero rankingsSource
Read a player's hero ranking scores and percentiles.
Player recent matches1
- List player recent matchesSource
Read a player's 20 most recent matches.
Player totals1
- List player totalsSource
Read lifetime totals (kills, deaths, gold ...) for a player.
Player win loss1
- Get player win/lossSource
Read a player's win and loss counts with optional filters.
Players2
- Get playerSource
Read a player's public profile name, rank tier and leaderboard rank.
- Search players by nameSource
Find public players by persona name.
Pro matches1
- List professional matchesSource
Read the most recent professional matches, newest first.
Pro players1
- List professional playersSource
Read professional players with their teams.
Public matches1
- List public matchesSource
Read a sample of recent public matches, optionally by rank tier.
Team matches1
- List team matchesSource
Read a team's recent matches.
Team players1
- List team playersSource
Read players who have played for a team.
Teams2
- Get teamSource
Read one team's rating and record.
- List teamsSource
Read teams ordered by rating.
Access and limits
- Authentication
- Public API (no credential)
- Plans and access
- Public OpenDota API. Public per-minute and daily quotas apply. Paid API-key access is not implemented because OpenDota accepts keys only as a query parameter.
- Test environment
- Public reference data; no provider-account validation recorded.
- Rate limits
- HTTP 429 uses bounded retries and Retry-After.
- Pagination
- Player match lists use limit and offset; pro and public match feeds page by less_than_match_id; teams page by a zero-based page of up to 1000.
- Provider events
- OpenDota has no webhooks. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Read only. Parse requests (POST /request/{match_id}), player refreshes, the SQL explorer and live feeds are excluded.
- API-key access is not implemented because OpenDota passes keys in the query string.
- Player data reflects only what the player exposes publicly on Steam and OpenDota; profile URLs, avatars and Steam IDs are not returned.
Developer reference
- Create the OpenDota credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose OpenDota, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/opendota and the Connections API.