Clash Royale icon

Clash Royale

Interact with Clash Royale API
Join our community

Actions17

Overview

This node interacts with the Clash Royale API to retrieve detailed information about clans, players, cards, tournaments, and other game-related data. Specifically, for the Clans resource with the Get River Race Log operation, it fetches the river race history of a specified clan. This is useful for tracking clan performance in river races over time, analyzing past results, or displaying recent clan activity related to river races.

Practical examples include:

  • Clan leaders monitoring their clan’s river race progress and history.
  • Community websites showing historical river race logs for clans.
  • Automated reports on clan performance trends in river races.

Properties

Name Meaning
Clan Tag The unique identifier (tag) of the clan without the # symbol. Example: Q9QQC902.
Additional Fields Optional parameters to refine the request:
- Limit Maximum number of river race log entries to return (minimum 1, default 50).
- After Return only river race log items that occur after this marker (pagination cursor).
- Before Return only river race log items that occur before this marker (pagination cursor).

Output

The node outputs JSON data representing the river race log of the specified clan. This includes an array of river race entries, each containing details such as timestamps, clan performance metrics, and possibly participant information.

If binary data were involved (not applicable here), it would be summarized accordingly, but this operation returns structured JSON data only.

Dependencies

  • Requires an active connection to the Clash Royale API.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL defaults to https://api.clashroyale.com/v1 unless overridden by credential settings.

Troubleshooting

  • Invalid Clan Tag: If the clan tag is incorrect or does not exist, the API will return an error. Ensure the clan tag is correct and does not include the # symbol.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key/token is correctly set up in the node credentials.
  • Rate Limits: The Clash Royale API enforces rate limits. Excessive requests may result in temporary blocking. Implement retries with backoff or reduce request frequency.
  • Pagination Issues: Using after and before markers incorrectly can lead to empty results or repeated data. Use these parameters carefully based on previous responses.

Links and References

Discussion