RoyaleAPI / cr-api

Clash Royale Analytics, Profiles and Insights. We no longer publish a public API. Please use the official API from Supercell.
https://RoyaleAPI.com
166 stars 20 forks source link

/player/{tags}/chests endpoint, always returns HTTP 400 #471

Closed Blind-Striker closed 4 years ago

Blind-Striker commented 4 years ago

Issue Report:

Did you encounter this recently, or has this bug always been there?

I have been trying this endpoint only for the last 3 days, I don't know if it exists before.

Expected behavior:

Should return multiple chests object within an array

Request Details:

GET  https://api.royaleapi.com/player/JGL2LGQ8,C280JCG/chests

Response Details:

HTTP/2 400 
date: Tue, 10 Sep 2019 10:33:40 GMT
content-type: application/json; charset=utf-8
content-length: 220
set-cookie: __cfduid=d0f0d7cdd5d4249805d85e744c002b9631568111620; expires=Wed, 09-Sep-20 10:33:40 GMT; path=/; domain=.royaleapi.com; HttpOnly; Secure
x-ratelimit-limit: 40
x-ratelimit-remaining: 39
via: 1.1 vegur
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 5140beb9a8daa7fe-IST
{
    "error": true,
    "statusCode": 400,
    "statusText": "Cannot fetch player chests: Cannot fetch player chests: tag 'JGL2LGQ8,C280JCG' is too long (min: 10)",
    "info": "Additional information and support: http://discord.me/royaleapi"
}
selfish commented 4 years ago

Endpoint re-implemented in v120, deploying now. Thanks for your report!