Yes, I already noticed that. According with the Publised-Data API page, timeout is 'timeout percentage' but in this case, what does it mean the value 100?? Myself have timeout=100 and I've lost rarely by timeout. Even in the case that the timeout displayed in the webpage is only over the last 90 days there is something weird with this data...
Bug: Team Match Endpoint- Issue with timeout
Sort:
Jan 2, 2018
0
#4
Thank you for noticing this issues, we are checking the source of this discrepancy and a fix should be out soon.
Jan 5, 2018
0
#6
The issue with players timeouts is fixed. Now this value match the one displayed in the webpage, timeouts of last 90 days, thanks!
Jan 5, 2018
0
#8
I need to partially correct my optimism... Some games are correct:
https://api.chess.com/pub/match/858116
But some not:
https://api.chess.com/pub/match/860030
Jan 6, 2018
0
#9
Dear @Dale00007 the fix will roll out Monday morning so since then you won't get correct results. Users stats should be already be fine but I'll wait until Monday to announce all the bug fixes that have been added these days.
Jan 8, 2018
0
#10
Breaking changes: please be aware that we have slightly changed the Team Match endpoint:
- We have added a "settings" property that contains most important match settings (rules, time_class, time_control etc.),
- we have renamed the "timeout" field of players to "timeout_percentage" in order to keep the same naming that we used in Player's stats endpoint.
Player timeout doesn't match timeout showed in stats on the webpage. For example:
https://api.chess.com/pub/match/857950
Player "susenka" - in endpoint timeout=100, but on webpage it is 6.25
Player "stanleymo" - in endpoint 6, webpage 0
Player "partiga" - in endpoint 13, webpage 0
Player "maxspachta" - in endpoint 100, webpage 15.76