OpenDota
Read the public Dota 2 hero catalogue for gaming analytics; no player accounts or wagering operations.
Read the public Dota 2 hero catalogue for gaming analytics; no player accounts or wagering operations.
Source actions
1
Destination actions
0
Data types
1
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
heroes
- List Dota 2 heroesSource
Read public game reference data.
heroes.list
Authentication
Public API (no credential)
Plans and access
Public OpenDota hero catalogue. Public quotas apply. Paid API-key authentication and other endpoints are not included.
Test environment
Public reference data; no provider-account validation recorded.
Rate limits
Provider account quotas apply; HTTP 429 uses bounded retries and Retry-After when supplied.
Pagination
Hero catalogue is a single array response.
Provider events
Not included in this read-only batch. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Fixture-tested implementation only; provider sandbox and authorised-account validation have not run.
- Only the listed reads are implemented. Writes, consent flows and automatic access-token refresh are not included.
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.