V3 Open Issues

[selfish]

Issues:

• ~https://v3-beta.royaleapi.com/clan/QPPPCYY/battles returns []~
• ~on the /players/ endpoint to specify which tag caused a 404~ (v128)

Feature-requests:

• Pagination
• ~multi-chests~ (v128)

[BlackHoleFox]

It seems like when you request a clan with /clan/tag/tracking and it isn't currently being tracked, it errors the server out instead of the expected response seen in the V2 docs

{
  "error": true,
  "statusCode": 500,
  "statusText": "Cannot fetch clan tracking: pg: no rows in result set",
  "eventId": "6b38ec108566470e89dd6a589c0a3fa6",
  "info": "Additional information and support: http://discord.me/royaleapi"
}

[BlackHoleFox]

On the /clan/<TAG>/history endpoint, the players in the members array are missing the lastSeen field. They exist in V2 and on most of the other responses that return player objects. See comparison with V2 below.

[BlackHoleFox]

The clanRank and rank fields are still separate on the /clan/history and /clan endpoints, even though it was listed as becoming unified on V82. The most recent war history snapshots show this:

[BlackHoleFox]

When using the /clan/search endpoint, any other query string except name returns a bad request error even though it matches the format shown in the V2 docs. Ex: https://v3-beta.royaleapi.com/clan/search?maxMembers=3 returns

  "error": true,
  "statusCode": 400,
  "statusText": "Failed to search clans: Failed to search clans: bad response: 400 Bad Request",
  "eventId": "8e28089d914e4479910f6e24a8209c56",
  "info": "Additional information and support: http://discord.me/royaleapi"
}

On a related note, all query strings in a request are ignored after name, such as /clan/search?name=abcd&minMembers=35 returns clans with less then 5 members.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.