And another month has gone by without a solution and no dialog.
Very disappointing.
I made another effort to get some update via chess.com support. This is what I've received on 2022-08-07:
I read your message and I understand how important this is for you. Please allow me to assist.
I personally asked our team about this and I'm really sorry to be the one to tell you this but based on what I learned this part of the API is probably going to remain limited. I would like to tell you more about it, but I'm afraid this is the only information I found and can share. I hope you understand. I would have shared more had I the liberty to do so.
... and here the follow-up that I've sent to chess.com support today:
What are you using to fill the variable 'country'?
It's the two-letter country code as defined here https://www.chess.com/news/view/published-data-api#pubapi-endpoint-country
This is not particularly informative, but at least chess.com support is still responding:
I reached out to our team about this and I found that we've taken your thoughts on board. Our developers are currently pursuing a long-term solution to this. I hope you can give us a bit more time on this one.
My apologies for not popping into this thread every so often.
I think my previous posts were misunderstood. As I had written, there is no easy way to make this endpoint work for larger countries with so many players, and the pagination idea is similarly dead in the water. We do not plan to update this endpoint. We DO want to help, though.
We noticed that this group of club owners are dedicated to recruiting interested players to their clubs. Your work using these endpoints has inspired a number of people on our product team to look at what targeted recruitment means and how to do that in a way that is approachable and powerful. We do not plan to spend the days trying to tune this endpoint because if we get it working perfectly this benefits maybe a dozen clubs serving about an eighth of our players — we'd rather spend the weeks or months of engineering time building tools that all club owners can use for all players to benefit from, magnifying the reach by hundreds.
Similar efforts are already in progress, and the work to make this new set of recruitment tools real is queued, but not yet in a development phase where we can predict when to expect it.
Can we provide input to how the targeted recruitment tool would work? I recruit for two completely different kinds of clubs.
1. Geographical based regional clubs, in both the US and Europe, where we want to search by flag/country and by words (city names) in the player's declared Location.
2. Competitive clubs where we want to search players by other criteria, such as rating, number of games played, time on the site, time out percentage, number of clubs, etc.
@bcurtis: What about a small addition to this request? Is it possible to add anything?
A "start_record" could be enough we need. A pack of 10000 records is OK if we can get next 10000 records starting from record number 10000. And so on : )
An update would be nice, I agree with @RathiDragon, just giving X first cant be a solution for a compagny like chess.com
My apologies for not popping into this thread every so often. [...]
Similar efforts are already in progress, and the work to make this new set of recruitment tools real is queued, but not yet in a development phase where we can predict when to expect it.
Apparently no progress? That's a pity.
I asked and there's not any update on it. A lot has changed in the last couple of years and there's nothing actively being planned on that front.
@Martin_Stahl: Thanks for posting. We appreciate that you return to this thread even with (as you will understand) frustrating news.
Does this mean that the whole idea of "a new set of recruitment tools" (@bcurtis) has been abandoned? How, then, chess.com thinks that clubs should proceed in recruiting players? I still cannot believe that it is impossible to make the necessary information available to interested team admins.
Another month has passed and no information about a resolution to this issue.
Any chance of an update?