Broken endpoint: https://api.chess.com/pub/club/{url-ID}/members

BTW - I'm not a member of Oracles

The member list itself is never viewable for private clubs, just the homepage listing of the admins.

Thanks Stephen. My bad. I had forgotten it was part of the club header endpoint. Cheers

Just the co-ordinators missing then.

"Just the co-ordinators missing then" - yes, and that's an ongoing source of irritation for me when teams nominate coordinators and I can't find them in any endpoint.

Why on earth omit them from the list of admins? Beats me.

Well, they are not admins, by definition.

But does that matter because they're able to perform basic admin functions. Doesn't that preclude them from being classed as nothing more than ordinary members?

I'd be fine with subdividing the "admin" category into "owner/SA", "ordinary_admin" & "coordinator" - who else would find that useful?

But they are public data.

Yes, it would be very useful.

Decided to take the plunge and now have a method of extracting club members.

Old method. One call to club menbers endpoint

New method. Call to club matches endpoint. One call to every match endpoint. Check all players against compiled list and add new.

Disadvantage: more calls and may pick up ex-members

Advantage: can be time restricted and filters for only recent match dates

You can browse back your member list to access their club list endpoint (provided it's still public) to verify if they are still in the club.

But it will only catch active members.

Yes. Not the same but better than nothing. And the auto filter for match active members is useful.

It also seperates out daily players and live players into seperate lists.

Been a while since anyone added to the list of broken club-members endpoints here but this one is causing me grief...

https://api.chess.com/pub/club/obsessive-chess-disorder/members

I've been asked to compile a new list of club members ranked by their participation in the club's matches but I need to have a list of current members so I don't include any that have left. Getting this predictable 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 ."}

I use the player's clubs endpoint to determine current membership.

https://www.chess.com/news/view/published-data-api#pubapi-endpoint-player-clubs

That's an option but it takes long enough to run through 500+ matches as it is without adding a hundred or more player endpoint downloads.

And if we have to re-code how we carry out functions every time an endpoint breaks, we're going to spend our lives doing that. There's no rush so I'm going to check that endpoint each day and hope it corrects soon.

As far as I understood it won't be fixed. Apparently it's a side effect of another change not related to the API and last I heard about it there was no indication they intended to revert it to the old behavior.

I hope I'm wrong though. That also broke the way I evaluate clubs in my league (trying to take active players into account but also inactive ones, which are hidden now) and I don't have a workaround for that.

And they call that "maintenance"? If that's the case, the way the staff of cdc use that term is very different from the way I do.