Other members have it so it's possible just an issue with the refresh on that member. I'll try to check later today to see if it updates in the endpoint refresh
Missing parameter in player Stats endpoint

Thanks Martin. I had hoped this would refresh however it has been like this for at least 48 hours on this member stats endpoint.

I put in a bug report at the same time as the OP. No response so far. Not even an acknowledgment of anything received. Support appears to be totally non existant now.

Richard, you have to wonder what the site means when it refers to the API being "maintained"?
At least I haven't found any broken club endpoints in the last few days, so have to be thankful for that I suppose 😉

Richard, you have to wonder what the site means when it refers to the API being "maintained"?
At least I haven't found any broken club endpoints in the last few days, so have to be thankful for that I suppose 😉
It means that if bugs happen due to other unrelated changes and effort will be made to fix the bugs. However, the API isn't getting direct development anymore and any changes are going to be ancillary to other projects

I put in a bug report at the same time as the OP. No response so far. Not even an acknowledgment of anything received. Support appears to be totally non existant now.
Unless you put in a ticket through the Support tool, staff don't normally acknowledge it unless they need additional information.
That said, staff are looking into why some members might be missing an RD value

Sadly another with exactly the same fault. So not just a one off. And also same TC. Rapid. Still no response from support.
https://api.chess.com/pub/player/victoras76/stats
"chess_rapid": { "last": { "rating": 1035, "date": 1736929232 },

Found out this apparently happens if there's an update to a rating by staff action and should be resolved if the impacted member plays a new game in the pool before the next endpoint refresh.
Staff are still looking into the issue to fix the problem when admin edits happen.

Sadly another with exactly the same fault. So not just a one off. And also same TC. Rapid. Still no response from support.
"chess_rapid": { "last": { "rating": 1035, "date": 1736929232 },This one is correct now:
"chess_rapid": {
"last": {
"rating": 1043,
"date": 1737637515,
"rd": 29

Thanks for the update, Martin. Good to know that one is fixed. Sounds as though the systems arn't sufficently robust and that more checking needed. Same issue with direct staff action causing faults with games archive status as reported here. https://www.chess.com/clubs/forum/view/error-in-player-game-archive

It won't be fixed until the member plays another Rapid game. They haven't played one since January 11th

And there's no easy method for any staff member to quickly repair a 'broken' endpoint when it's brought to their attention?

The data isn't there from where the endpoint pulls from and would require a manual DB insert. That's not something that's likely to happen for a few members when it will automatically update at the endpoint refresh after the next time a game in the pool is played

Perhaps fixing the bug that creates the issue, rather than ignoring the problem. Just a thought.
Seems 'Maintainance mode' means 'Don't care about the problems'

Staff are aware of what seems to cause it, which likely will get fixed at some point, but also is not a high priority.

and another one
https://api.chess.com/pub/player/benblunderer/stats
No RD in bullet stats. Maintainence mode is less than helpful.

And another: missing in rapid
https://api.chess.com/pub/player/matthewpbr/stats
again
https://api.chess.com/pub/player/marsmonolith/stats Rapid
Spec for endpoint https://api.chess.com/pub/player/{username}/stats