Is it just the documentation that's a problem with that Richard, because that limit on finished matches was introduced a couple of years ago now.
I remember it being a minor nuisance at the time because it wasn't possible anymore to perform a simple loop over the endpoint keys of "registered", "in_progress" and "finished".
Agreed, Stephen. Another example of how the control of the system is failing.
It's far from ideal when the site makes unannounced changes to the API and we suddenly find our carefully constructed scripts don't work anymore but it's usually possible to fix things without a huge amount of effort.
What's far worse is when changes are made that break some part of the API and no one seems able to fix it - for example timeout rates in matches and player endpoints. That's what pushes my blood pressure up.
The rest we can work around but what do you do when the developers seem to be sabotaging their own site?
When you make breaking changes to an API, obviously you document them, at least if you claim to be supporting your API.
The CHANGELOG has been neglected for so long now that it wouldn't occur to me to look there if something changes in the API. Provided I can identify the problem and put a fix in place I'm reasonably happy.
It's problems like the non-matching timeout rates between webpages and endpoints, that has only just been corrected, and the ongoing (I think) problem with the club/members endpoints that are worse headaches because it's not easy to work around them.
Returns this comment at the end of the string, following Registration matches.
,"comment":"Results are temporarily reduced to the most recent 500 matches for performance reasons"
This is not shown in the spec for the end point as far as I can see.