Heroes Profile icon

Heroes Profile

Get data from Heroes Profile API and normalize it into REST API style JSON

Actions26

Hero → Build Stats

AI-generated

Overview

The "Build Stats" operation for the "Hero" resource in this node fetches detailed statistics about hero builds from the Heroes Profile API. It allows users to retrieve data on how different heroes are built in various game types and patches, providing insights into popular talent choices and strategies.

This node is beneficial for players, analysts, or content creators who want to analyze hero build trends, compare builds across different game modes, or track changes over time with patch updates. For example, a user could select a specific hero and game type to get the most common talent builds used by top players during a particular patch.

Properties

Name Meaning
Hero Select a hero to get build stats for. Options include all available heroes like Abathur, Jaina, etc.
Mode Response format of the data: either JSON or CSV.
Game Type The type of game mode to filter stats by, e.g., Quick Match, Hero League, ARAM, etc.
Timeframe Type Patch type to filter data by: Major or Minor patch.
Timeframe Specific patch number to filter the data (e.g., "2.55"). You can use the 'Get patch metadata' operation to find valid patch numbers.

Output

The output is a JSON object (or CSV if selected) containing normalized hero build statistics retrieved from the Heroes Profile API. This includes data such as popular talent choices, their pick rates, win rates, and possibly other aggregated metrics related to hero builds for the specified filters.

If CSV mode is selected, the output will be a CSV string representing the same data.

No binary data output is involved.

Dependencies

  • Requires an API key credential for the Heroes Profile API.
  • The node makes HTTP requests to https://api.heroesprofile.com/api.
  • No additional environment variables are required beyond the API authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Providing an invalid patch number or timeframe may result in empty or error responses.
    • Selecting unsupported combinations of parameters might yield no data.

  • Error messages:

    • Authentication failures: Check that the API key credential is correctly configured.
    • "Invalid timeframe" or similar errors: Verify the patch number using the 'Get patch metadata' operation.
    • Network errors: Ensure internet connectivity and that the API endpoint is reachable.

Links and References

Discussion