[Bug report] 404 status code with an internal error message

Sort:
remyrouyer

Bug Report

Summary:
The Chess.com API games/archives endpoint for specific users (imrosen and remyrouyer) exhibits inconsistent behavior. While most archive links work as expected, a subset of URLs (listed below) return a 404 status code with an internal error message.


Steps to Reproduce:

  1. Request the monthly archive endpoints for the user remyrouyer:
    https://api.chess.com/pub/player/remyrouyer/games/archives

  2. Request the specific monthly archives for the user imrosen:

  3. Compare these to other valid archive links returned by https://api.chess.com/pub/player/imrosen/games/archives. For example:


Actual Behavior:
The following endpoints return a 404 status code with an internal error message:

Response:

{ "code": 0,
"message": "An internal error has occurred. Please contact Chess.com Developer's Forum for further help https://www.chess.com/club/chess-com-developer-community." }

Other archive URLs for imrosen work as expected. For example:

Wizriks

yo

Wins

I just had the same problem

Astro_Pup

when i restarted my safari i logged on to chess.com and it had a server error

Wins

going off the endpoint stated in: https://www.chess.com/news/view/published-data-api#pubapi-endpoint-games-archive-list

The example: https://api.chess.com/pub/player/erik/games/archives seems to be the only thing working. However for usernames such as my own (or any other player for that matter) ... 
https://api.chess.com/pub/player/wins/games/archives

{"code":0,"message":"An internal error has occurred. Please contact Chess.com Developer's Forum for further help https://www.chess.com/club/chess-com-developer-community ."}
 
ninjaswat

#5, the link you just sent returns a code of 0 rather than 404, so that might be a separate error altogether. I checked @IMRosen's page and couldn't search games using the website for the interval that was broken, so could it be that some part of game history itself is broken?

remyrouyer
wrote:

#5, the link you just sent returns a code of 0 rather than 404, so that might be a separate error altogether. I checked @IMRosen's page and couldn't search games using the website for the interval that was broken, so could it be that some part of game history itself is broken?

Seems to be a HTTP Status Code 404, but also it returns a json body that has a separate "code" being 0

remyrouyer
ninjaswat wrote:

#5, the link you just sent returns a code of 0 rather than 404, so that might be a separate error altogether. I checked @IMRosen's page and couldn't search games using the website for the interval that was broken, so could it be that some part of game history itself is broken?

And I was able to view imrosen's games during the timeframe where the api is broken through the website search.

Wins
ninjaswat wrote:

#5, the link you just sent returns a code of 0 rather than 404, so that might be a separate error altogether. I checked @IMRosen's page and couldn't search games using the website for the interval that was broken, so could it be that some part of game history itself is broken?

Seems like the same problem as the poster of this forum as he also also stated in the inital post that his response was:

{ "code": 0,
"message": "An internal error has occurred. Please contact Chess.com Developer's Forum for further help https://www.chess.com/club/chess-com-developer-community." }
Wins

The error message when done programmatically is what the title is referring to

Martin_Stahl

Are you still seeing the issue. There was pretty big issue earlier causing problems in different areas of the site and should be resolved now.

Wins
Martin_Stahl wrote:

Are you still seeing the issue. There was pretty big issue earlier causing problems in different areas of the site and should be resolved now.

Seems like more work but some still dont

AmatraX

I have the same problem...

https://api.chess.com/pub/player/amatrax/games/2025/04

https://api.chess.com/pub/player/uglavan/games/2025/04

Martin_Stahl

That's different than a 404 and will likely resolve at the next endpoint update

AmatraX
je napisal/-a:

That's different than a 404 and will likely resolve at the next endpoint update

Thank you for your respond. It is fixed now for current month. What about for previous months? Will it fix?

Martin_Stahl

Endpoints periodically update. I can't say for sure when any particular one might. If they are still having issues in 12 hours post the specific endpoints and I can find out if there may be some back-end issue.

remyrouyer
wrote:

Endpoints periodically update. I can't say for sure when any particular one might. If they are still having issues in 12 hours post the specific endpoints and I can find out if there may be some back-end issue.

My archives endpoint did get resolved, but these monthly archive endpoints for imrosen have still not resolved after 12 hours.