Several requests for API changes

Sort:
Storms-Fast

I would find the following changes useful 

  1. New endpoint that returns all closed accounts per country (the current endpoint only returns active accounts); preferably in a paged fashion (100k at a time, ordered by player_id)
  2. Endpoint that returns all 'players' per country in a paged fashion ordered by player_id i.e. you can request say 100,000 players at a time rather than the full shabang (the US times out if you request all players)
  3. New endpoint that returns player details in batches; e.g. you pass in 100 member names and get a response that contains 100 player details (e.g. array / one JSON object keyed on player name)
  4. For accounts that have a status of 'closed:fair_play_violations' - also add details of the violation; e.g. engine or sandbagging
CyberSensei

I'm not sure the policy has changed regarding other member's accounts, however, sharing details about "why" accounts are closed is not permitted. We will have to wait to hear what beta admin ruling.

For more information, see this link (https://www.chess.com/forum/view/community/discussions-about-cheating)

Storms-Fast
CyberSensei wrote:

I'm not sure the policy has changed regarding other member's accounts, however, sharing details about "why" accounts are closed is not permitted. We will have to wait to hear what beta admin ruling.

For more information, see this link (https://www.chess.com/forum/view/community/discussions-about-cheating)

well the API already tells you 'why' an account was closed from the status; e.g. one of the status is 'closed:fair_play_violations'

So from the status we already know that it was closed due to 'fair play violations' aka cheating. Seen as we already know that it was closed due to cheating I don't think giving the method of cheating would be an issue.

Martin_Stahl
EdanLeung-ChessBot wrote:
Storms-Fast wrote:

I would find the following changes useful 

  • New endpoint that returns all closed accounts per country (the current endpoint only returns active accounts); preferably in a paged fashion (100k at a time)
  • Endpoint that returns all 'players' per country in a paged fashion i.e. you can request say 100,000 players at a time rather than the full shabang (the US times out if you request all players)
  • New endpoint that returns player details in batches; e.g. you pass in 100 member names and get an array / json object of 100 player details
  • For accounts that have a status of 'closed:fair_play_violations' - also add details of the violation; e.g. engine or sandbagging

The suggestions where you said

"For accounts that have a status of 'closed:fair_play_violations' - also add details of the violation; e.g. engine or sandbagging"

 

would be useful

 

As far as I'm aware, that data isn't directly tracked. All FPV are the same from an account standpoint.

Storms-Fast
Martin_Stahl wrote:

As far as I'm aware, that data isn't directly tracked. All FPV are the same from an account standpoint.

OK I see.. if it's not in the database then I retract that request. TBH I'd be surprised if any of the requests get actioned  - worth asking though!