There's no question - there's a problem with the list of club finished matches. I've been looking at this club's archive...
https://api.chess.com/pub/club/team7/matches
The match start dates range from Nov 29 2010 to Jun 21 2012 with none of the most recent matches in the listing. There's obviously a problem here and I've reported it.
Two months have past. Bug is still not fixed.
I reported this to the staff on the 17th/April and now that I've checked I realise I never received a response (from a human being that is). I also reported the problem with accessing certain match endpoints on the same day, so I have a feeling a staff member probably mistook the '500 most recent matches' glitch for the other difficulty?
It seems the most likely explanation. I use the club match archive of finished matches for only one thing I do in just one club and it hasn't yet hit the 500 match limit.
That said, I'll re-report it and chase them to get something done.....
As many of you know, starting from the 8th of March API returns not the full list of team matches, but the trimmed list of them. From the news ( https://www.chess.com/news/view/non-breaking-change-club-matches-endpoint ) we expect to have a following structure of the endpoint:
{
"finished": [ 1000* most recent matches ],
"in_progress": [ All in progress matches ],
"registered": [ All registered matches],
"comment": "Results are temporarily reduced to the most recent 1000 matches for performance reasons"
}
* In fact it was reduced later to 500, as it is said in "comment" section now.
Obtained JSON has the expected structure:
So at number #499 (500th daily match) we have a match that was finished 9 years ago.
And then, starting from number 500, finished live matches are placed. We currently have only 476 live matches played, so I don't know: will this bug be reproduced for live section as well or not, when we pass the limit of 500 matches.
Concluding, there is no currently a way to obtain a list of recently finished matches for your team, if more than 500 matches were played.
P.S. Using the opportunity, I repeat my unanswered question published under the related news ( https://www.chess.com/news/view/non-breaking-change-club-matches-endpoint#comment-58266362 ):
Does "temporarily" means that you plan to return full functionality for the endpoint later on? If so, could you give an approximate timescale? A month later? A year?
Wouldn't it be better to separate this endpoint by two ( /pub/club/{ID}/lastmatches and /pub/club/{ID}/allmatches ), asking developers to use only first one, if possible?