hey bud this is complete jargon to me that i dont understand. please explain if its important
Bug in team match end point - FPV list

hey bud this is complete jargon to me that i dont understand. please explain if its important
If you're not using the team match endpoint, it's not important. If you are and aren't using the list of fair play violations closures, it's not important.
It's not really written in jargon; as you become familiar with pulling out specific portions of the data from the JSON returned from api.chess.com, it'll be easy to understand. The specific problem reported is a missing data in one match's details.

@Tricky_Dicky thanks for heads up. This isn't actually a bug, but it reflects how we calculate player's status and match fair_play_violations :
- status : reflects the current status of the user, as displayed in other endpoints;
- fair_play_removals : shows if the players account was blocked during the match.
So, in this case, the match started on 26/11/2018 and ended 10/02/2019 (all dates are in DD/MM/YYY format).
There are two players in this match that have a status of "closed:fair_play_violations": bigphil_yorks and robbie57 :
- bigphil_yorks account was closed on 11/03/2019, after the match ended, so he isn't listed in fair_play_removals,
- robbie57 account was closed on 27/12/2018, during the match, so he is listed in fair_play_removals
We can, of course, rethink this decision if you find it not useful for your needs.
This may be an isolated incident.
https://api.chess.com/pub/match/947106
Username @bigphil_yorks
status: "closed:fair_play_violations"
Not listed in "fair_play_removals" at end of data string