Heroes Profile icon

Heroes Profile

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

Player → Replays

AI-generated

Overview

The "Player Replays" operation of the Heroes Profile node fetches replay data for a specific player from the Heroes Profile API. This allows users to retrieve detailed match replay information filtered by various parameters such as hero played, game type, and region. It is useful for players or analysts who want to review gameplay history, analyze performance trends, or gather data for coaching and improvement.

Practical examples include:

  • Retrieving all replays of a player playing a particular hero.
  • Filtering replays by game mode (e.g., Quick Match or Hero League).
  • Exporting replay data in JSON or CSV format for further analysis.

Properties

Name Meaning
Hero Select a hero to filter replays by that hero. Options include all available heroes like Abathur, Jaina, Zeratul, etc.
Mode Select the response format: JSON or CSV.
Game Type Filter replays by game type. Options include Quick Match, Unranked Draft, Hero League, Team League, Storm League, ARAM.
Battletag The player's battletag to identify which player's replays to fetch.
Region The region where the player plays. Options include North America, Europe, Korea, China.

Output

The output consists of JSON data representing the player's replay information according to the selected filters. The structure typically includes details about each replay such as match ID, hero played, game mode, date/time, and other relevant statistics. If CSV mode is selected, the output will be in CSV format containing similar data fields.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for the Heroes Profile API.
  • The node makes HTTP requests to https://api.heroesprofile.com/api.
  • Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

  • Missing or invalid API key: The node will fail if the API key credential is not set or invalid. Ensure the correct API key is configured.
  • Invalid battletag or region: Providing incorrect battletag or region values may result in no data or errors. Verify inputs carefully.
  • Empty results: If no replays are returned, check if the filters (hero, game type) are too restrictive or if the player has no matching replays.
  • API rate limits: Excessive requests might lead to throttling by the Heroes Profile API. Implement delays or retries as needed.

Links and References

Discussion