This is an undocumented API limitation that was imposed earlier this year (or was it last year already?) : this API endpoint will return an error if the club has a private members list. Of course the error code doesn't match. And the feedback I had was that's the side effect of some other change but they don't seem to be in a mood to revert it.
Club Api Calls Fail
I remember that and I argued that it should return a "403" (access prohibited) rather than the "404" (page not found) because it's more appropriate. I can imagine someone might waste a lot of time establishing exactly why they can't access an endpoint.
As usual it fell on deaf ears.
API endpoint will return an error if the club has a private members list.
Looks right but here is a different problem.
https://api.chess.com/pub/club/improvers/members FAILS with different Code
Private Club with Public Member list.
| code | 3024 |
| 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 ." |
I seem to remember encountering code 3024 before and it's provided by Cloudflare, not the site's servers. When I search I can't find it though, so I may be wrong?
Or this https://api.chess.com/pub/club/chess-com-community/members FAILS
Public Club with Public Member list same code
| code | 3024 |
| 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 ." |
Promote to King has it's member list set to private. This stops the API endpoint from returning a valid list and as C.C can't be bothered with the API anymore there is no sensible data information.
It is an intentional feature without any proper return information.
Something not right there Allen? Although when I check it with an endpoint I use a lot...
https://api.chess.com/pub/club/team-match-championship-league/members
... no problem. Same with other ones I use.
I remember that and I argued that it should return a "403" (access prohibited) rather than the "404" (page not found) because it's more appropriate. I can imagine someone might waste a lot of time establishing exactly why they can't access an endpoint.
As usual it fell on deaf ears.
agree
Something not right there Allen? Although when I check it with an endpoint I use a lot...
https://api.chess.com/pub/club/team-match-championship-league/members
... no problem. Same with other ones I use.
Do any have over 1000 members? Countries go to 10000 maybe they are off by a decimal place.
https://api.chess.com/pub/club/promote-to-king/members FAILS
https://api.chess.com/pub/club/grand-tourneys/members Works
I think it is due to the number of members in the club.
But countries work great. i.e. https://api.chess.com/pub/country/US/players