Heroes Profile icon

Heroes Profile

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

Actions26

Replay → After ID

AI-generated

Overview

The "After ID" operation under the "Replay" resource in this node is designed to fetch replay data starting from a specified earliest replay ID. This allows users to retrieve game replay information incrementally, beginning at a particular point in the replay history. It is useful for scenarios such as analyzing recent matches, updating databases with new replays since a known replay ID, or filtering replays by game type.

For example, a user might want to collect all replays after replay ID 1000000 for the "Hero League" game type to analyze player performance trends in ranked matches.

Properties

Name Meaning
Game Type Select the type of game to filter replays by. Options include: Quick Match, Unranked Draft, Hero League, Team League, Storm League, ARAM. If left empty, no game type filtering is applied.
Earliest Replay ID The minimum replay ID to start fetching from. Only replays with IDs greater than or equal to this value will be returned. This property is required and must be a number.

Output

The node outputs JSON data representing the replay information retrieved from the API. The structure typically includes details about each replay such as replay ID, game type, players involved, match statistics, and other metadata normalized into a REST API style JSON format.

No binary data output is indicated in the provided code or properties.

Dependencies

  • Requires an API key credential for authentication with the Heroes Profile API.
  • The base URL for API requests is https://api.heroesprofile.com/api.
  • The node expects JSON responses and sends requests with appropriate headers (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Missing or invalid API credentials: Ensure that a valid API key credential is configured in n8n for the Heroes Profile API.
  • Invalid or missing Earliest Replay ID: Since this property is required, leaving it empty or providing a non-numeric value will cause errors. Always provide a valid numeric replay ID.
  • No replays returned: This can happen if the specified replay ID is too recent or if the game type filter excludes all available replays. Try adjusting the replay ID or removing the game type filter.
  • API rate limits or connectivity issues: Network problems or hitting API rate limits may cause request failures. Check network connectivity and API usage quotas.

Links and References

Discussion