Actions17
- Clans Actions
- Players Actions
- Tournaments Actions
- Locations Actions
- Leaderboards Actions
Overview
This node interacts with the Clash Royale API to retrieve player rankings for a specified location. It is useful for scenarios where you want to analyze or display leaderboard data filtered by geographic regions, such as showing top players in a country or city. For example, a gaming analytics dashboard could use this node to fetch and present the top-ranked players in a particular location.
Properties
| Name | Meaning |
|---|---|
| Location ID | Identifier of the location to get player rankings from (e.g., a country or city code). |
| Additional Fields | Optional parameters to refine the query: - Limit: Max number of results to return. - After: Return only items after this marker (pagination). - Before: Return only items before this marker (pagination). |
Output
The node outputs JSON data representing the player rankings for the specified location. The structure typically includes an array of player ranking objects, each containing details such as player tag, name, rank, trophies, and other relevant stats. If pagination parameters are used, the output may also include markers for navigating through pages of results.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the Clash Royale API.
- The base URL defaults to
https://api.clashroyale.com/v1but can be overridden via credentials configuration. - Network access to the Clash Royale API endpoint is necessary.
Troubleshooting
- Invalid Location ID: If the location ID is incorrect or does not exist, the API may return an error or empty results. Verify the location identifier.
- API Authentication Errors: Missing or invalid API key will cause authentication failures. Ensure the API key credential is correctly configured.
- Rate Limiting: The Clash Royale API enforces rate limits; excessive requests may result in temporary blocking. Implement retries or backoff strategies if needed.
- Pagination Issues: Using
afterandbeforemarkers incorrectly may lead to unexpected results or empty responses. Use these parameters carefully according to API documentation.