Docs menu

OpenDota API endpoint

OpenDota Aghanim descriptions API

Returns, for every Dota 2 hero or for one `hero_id`, what Aghanim's Scepter and Aghanim's Shard do: whether each upgrade exists, its description, the skill it changes and whether it adds a new skill. `include_lore=true` adds each hero's lore text (about 155 KB for all heroes), so it is off by default. An unknown hero id returns not found. Take `hero_id` from opendota-heroes.

GETapiKey2 credits/requestOpenDota/opendota/hero-descriptions

Endpoint facts

Method: GET
API path: /opendota/hero-descriptions
Auth: apiKey
Credits: 2 credits/request
Charged on: Successful 2xx responses only
Platform: OpenDota

OpenDota API for Dota 2 Data Try OpenDota Aghanim descriptions API in Playground OpenDota API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

hero_id: optional positive hero id from opendota-heroes; omit it for all 127 heroes. An id with no Aghanim description returns 404.
include_lore: optional; true adds each hero's lore text in lore (about 155 KB for all heroes). Defaults to false.

Notable response behavior:

Each hero has hero_id, name (the internal npc_dota_hero_* name), key (the name without the prefix, which is also the lore key), scepter and shard. Each upgrade has available, description, skill_name (the ability it changes) and new_skill (true when the upgrade adds an ability).
A hero with no Scepter or Shard upgrade has available: false and an empty description. Descriptions are the tooltip text from the game files and can contain % placeholders for values.
With include_lore=false the lore table is not fetched at all.
Built from the dotaconstants tables aghs_desc and hero_lore. The response is cached for up to a day and costs two credits.

Sampled response

Request, 29 Oct 2026: GET /opendota/hero-descriptions?hero_id=1
Items in heroes: 1
Fields filled in every checked item: 5

Field	Filled in, of 1 checked	Values in the sample
hero_id	1
name	1	“npc_dota_hero_antimage”
key	1
scepter	1
shard	1

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
hero_id	integer	No		Positive hero id from opendota-heroes; omit it for all heroes Minimum: 1.	1
include_lore	boolean	No	false	true adds each hero's lore text; defaults to false

cURL example

curl -X GET "https://api.crawlora.net/api/v1/opendota/hero-descriptions?include_lore=true" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/constants/aghs_desc",
    "fetched_at": "2026-10-29T10:00:00Z",
    "hero_id": 1,
    "include_lore": true,
    "count": 1,
    "heroes": [
      {
        "hero_id": 1,
        "name": "npc_dota_hero_antimage",
        "key": "antimage",
        "scepter": {
          "available": true,
          "description": "After casting Blink, your next Mana Break within 5s burns an additional 20% max mana and prevents the target from regenerating or gaining mana for a short durat ...",
          "skill_name": "Blink",
          "new_skill": false
        },
        "shard": {
          "available": true,
          "description": "Creates a blinked fragment of Anti-Mage next to the enemy caster upon reflecting their unit-targeted spell while active. ...",
          "skill_name": "Counterspell",
          "new_skill": false
        },
        "lore": "The monks of Turstarkuri watched the rugged valleys below their mountain monastery as wave after wave of invaders swept through the lower kingdoms. Ascetic and  ..."
      }
    ]
  }
}

Request schema

No body schema

Response schema

Inline response schema

Field	Type	Required	Example	Description
code	integer	No		Code is the HTTP status code or a custom code used to indicate the result of the request @example 200
data	opendota.HeroDescriptionsResponse	No
data.count	integer	No	127
data.fetched_at	string	No	2026-10-27T10:00:00Z
data.hero_id	integer	No	1
data.heroes	array	No
data.heroes[].hero_id	integer	No	1
data.heroes[].key	string	No	antimage
data.heroes[].lore	string	No
data.heroes[].name	string	No	npc_dota_hero_antimage
data.heroes[].scepter	opendota.AghanimUpgrade	No
data.heroes[].scepter.available	boolean	No	true
data.heroes[].scepter.description	string	No
data.heroes[].scepter.new_skill	boolean	No	false
data.heroes[].scepter.skill_name	string	No	Blink
data.heroes[].shard	opendota.AghanimUpgrade	No
data.heroes[].shard.available	boolean	No	true
data.heroes[].shard.description	string	No
data.heroes[].shard.new_skill	boolean	No	false
data.heroes[].shard.skill_name	string	No	Blink
data.include_lore	boolean	No	false
data.source_url	string	No
msg	unknown	No		Msg is the message that describes the result of the request @example "Request successful"

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
404	Not Found	#/definitions/app.Response
429	Too Many Requests	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/opendota/hero-descriptions?include_lore=true" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More OpenDota endpoint docs OpenDota API for Dota 2 Data OpenDota Ability Directory API documentation OpenDota Benchmarks API documentation OpenDota constants lookup API documentation OpenDota matches by hero lineup API documentation OpenDota Hero Abilities API documentation OpenDota hero durations API documentation

Open in Playground Back to group

Docs menu

OpenDota API endpoint

OpenDota Aghanim descriptions API

GETapiKey2 credits/requestOpenDota/opendota/hero-descriptions

Endpoint facts

Method: GET
API path: /opendota/hero-descriptions
Auth: apiKey
Credits: 2 credits/request
Charged on: Successful 2xx responses only
Platform: OpenDota

OpenDota API for Dota 2 Data Try OpenDota Aghanim descriptions API in Playground OpenDota API documentation

How this endpoint behaves

Header: x-api-key required.

Parameters:

hero_id: optional positive hero id from opendota-heroes; omit it for all 127 heroes. An id with no Aghanim description returns 404.
include_lore: optional; true adds each hero's lore text in lore (about 155 KB for all heroes). Defaults to false.

Notable response behavior:

Each hero has hero_id, name (the internal npc_dota_hero_* name), key (the name without the prefix, which is also the lore key), scepter and shard. Each upgrade has available, description, skill_name (the ability it changes) and new_skill (true when the upgrade adds an ability).
A hero with no Scepter or Shard upgrade has available: false and an empty description. Descriptions are the tooltip text from the game files and can contain % placeholders for values.
With include_lore=false the lore table is not fetched at all.
Built from the dotaconstants tables aghs_desc and hero_lore. The response is cached for up to a day and costs two credits.

Sampled response

Request, 29 Oct 2026: GET /opendota/hero-descriptions?hero_id=1
Items in heroes: 1
Fields filled in every checked item: 5

Field	Filled in, of 1 checked	Values in the sample
hero_id	1
name	1	“npc_dota_hero_antimage”
key	1
scepter	1
shard	1

Request parameters

Parameter	Type	Required	Default	Description	Example
x-api-key (header)	string	Yes		API key required
hero_id	integer	No		Positive hero id from opendota-heroes; omit it for all heroes Minimum: 1.	1
include_lore	boolean	No	false	true adds each hero's lore text; defaults to false

cURL example

curl -X GET "https://api.crawlora.net/api/v1/opendota/hero-descriptions?include_lore=true" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://api.opendota.com/api/constants/aghs_desc",
    "fetched_at": "2026-10-29T10:00:00Z",
    "hero_id": 1,
    "include_lore": true,
    "count": 1,
    "heroes": [
      {
        "hero_id": 1,
        "name": "npc_dota_hero_antimage",
        "key": "antimage",
        "scepter": {
          "available": true,
          "description": "After casting Blink, your next Mana Break within 5s burns an additional 20% max mana and prevents the target from regenerating or gaining mana for a short durat ...",
          "skill_name": "Blink",
          "new_skill": false
        },
        "shard": {
          "available": true,
          "description": "Creates a blinked fragment of Anti-Mage next to the enemy caster upon reflecting their unit-targeted spell while active. ...",
          "skill_name": "Counterspell",
          "new_skill": false
        },
        "lore": "The monks of Turstarkuri watched the rugged valleys below their mountain monastery as wave after wave of invaders swept through the lower kingdoms. Ascetic and  ..."
      }
    ]
  }
}

Request schema

No body schema

Response schema

Inline response schema

Field	Type	Required	Example	Description
code	integer	No		Code is the HTTP status code or a custom code used to indicate the result of the request @example 200
data	opendota.HeroDescriptionsResponse	No
data.count	integer	No	127
data.fetched_at	string	No	2026-10-27T10:00:00Z
data.hero_id	integer	No	1
data.heroes	array	No
data.heroes[].hero_id	integer	No	1
data.heroes[].key	string	No	antimage
data.heroes[].lore	string	No
data.heroes[].name	string	No	npc_dota_hero_antimage
data.heroes[].scepter	opendota.AghanimUpgrade	No
data.heroes[].scepter.available	boolean	No	true
data.heroes[].scepter.description	string	No
data.heroes[].scepter.new_skill	boolean	No	false
data.heroes[].scepter.skill_name	string	No	Blink
data.heroes[].shard	opendota.AghanimUpgrade	No
data.heroes[].shard.available	boolean	No	true
data.heroes[].shard.description	string	No
data.heroes[].shard.new_skill	boolean	No	false
data.heroes[].shard.skill_name	string	No	Blink
data.include_lore	boolean	No	false
data.source_url	string	No
msg	unknown	No		Msg is the message that describes the result of the request @example "Request successful"

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
404	Not Found	#/definitions/app.Response
429	Too Many Requests	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/opendota/hero-descriptions?include_lore=true" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

Open in Playground Back to group

OpenDota Aghanim descriptions API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

OpenDota Aghanim descriptions API

Endpoint facts

How this endpoint behaves

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related