Endpoints for Public Club Data

It would be nice if there was at least some way to access the public data and what better then through the API. The specific data I am looking for is club "Members" and "Top Players". Possibly even "Daily Matches" and "Vote Chess". 

Timeouts, rating, nationality etc etc

I'm looking for member ratings to compare over time looking for unusually fast changes either up or down; perhaps by group to limit the data returned.

A player's nationality is actually already provided: https://api.chess.com/context/Player.jsonld

For club administrators, a method is needed that returns a list of players who meet a few filters, timeout, nationality, daily stats ... The important thing is to be a list to be able to quickly review certain players. In that list could come the url of the players.

List of players signed up for a match. (To balance boards, maybe look up individual players' timeout figures -- some competitions allow removal of players with too-high timeout percentages.)

Once underway or complete access to current results, ideally with losses due to timeouts marked and perhaps closed accounts marked some way, especially those closed for "Fair Play" violations.

P.S. This is my first look around and first post. If what I'm looking for is available and documented here already, please be gentle. I believe I've read most of the documentation and a lot of the threads, but if I've missed something, I apologise in advance.

Vote chess games, and who is signed up for them.

I would like a vote cast in a vote chess game to count as "activity" in the club, too.

(I would prefer that "activity" were differently defined; posting a note is one thing, but inviting people is different, as is signing up for a match, as is signing up for a vote chess game. But if we keep the week/month/remainder split of users, voting in a vote chess game should count IMHO. Probably having an unfinished game in a team match, too.)

I guess my second point is I'd like "activity" to be much more precisely documented, even if the functionality and documentation are revised as we all gain more experience with this API.