It's probably the bulk send. Better to do them sequentially waiting for a response before sending another request.
CORS error while requesting games

It's probably the bulk send. Better to do them sequentially waiting for a response before sending another request.
CORS errors are not typical for rate limiters. Even documentation mentions that their server will respond with HTTP 429 in this case: https://www.chess.com/news/view/published-data-api#pubapi-general-rate-limits
Hi,
I'm using the following endpoint:
https://www.chess.com/news/view/published-data-api#pubapi-endpoint-games-archive
Upon making a request, it sometimes throws a CORS error:
Access to fetch at 'https://api.chess.com/pub/player/username/games/2019/09' from origin 'http://localhost:1234' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
What's interesting, is that upon a couple of retries, it no longer throws this error. After 5-6 retries I'm able to have all requests come through. I could retry them till success, but it's not an elegant solution.
I'm trying to get all games for a player, so I'm sending these requests basically in bulk. It does not seem connected, but worth noting nonetheless.
Could you please advise on a solution for that?
On an unrelated note, is there a "dummy" player account, that I can use to test my API?