Bugs in Club Team Match

Two problems in end point https://api.chess.com/pub/match/{ID} 

1)

status : closed. 

This is not part of the specification.

2)

Items in red missing from player information

"username": "username", 
                    "board": "url", // url of board
                    "rating": 1355, //rating of player
                    "rd": 25.12, //Glicko RD
                    "timeout_percent": 25.12, //timeout percentage in the last 90 days
                    "status": "basic" //status of user

Example

https://api.chess.com/pub/match/995756

I had one of those matches too but I think the staff must have corrected your one already because it's changed to "status":"in_progress"

It's been 7-hours since your post.

When I click the example link:

• I see "board"
• I see "timeout_percent"
• Neither of which are an issue (IMO)

• I don't see "rating"
• I don't see "rd"
• Spec is outdated or wrong.

When I follow the "stats" (JSON-LD) URL for a player, I do see "rating" and "rd" for the variant or time-control. If the "rating" and "rd" should be frozen for a team mach, I don't see a problem. If they're revolving, then, just follow the (JSON-LD) stats link for the player, followed by the respective time control or variant. (As a temporary workaround. The Published API should be updated to reflect whatever change.)

Notify:

• https://www.chess.com/news/view/published-data-api
• https://www.chess.com/clubs/forum/view/minor-documentation-errata
• pushed link to both.

Player ratings are given in matches with status "registration" but not "in_progress" & the match cited is now in the latter stage.

* I remember asking a few months ago for player ratings to be provided in matches "in_progress" & one of the developers made a favourable comment but it hasn't happened yet.

I think you are correct Stephen.

I was looking at the registration phase spec.

My code is now working again without mod. I suspect it was a time lag issue. When I ran the program yesterday it was just after the match had started. However I don't understand the "Closed" status. I can only assume there is an intermediate stage while the API updates from registration to in_progress.

Did you see the topic I started when this happened to me?

https://www.chess.com/clubs/forum/view/this-is-strange

andreamorandini gave an explanation of what went wrong with the processing of the match. It's status seems to have been left 'hanging' as it progressed from registration to in-progress. That's two matches now within a week or so & I'm not sure if we're supposed to dismiss it as an anomaly or whether we need to provide for it in our scripts?

Thanks Stephen. I do now remember your post but hadn't clicked follow so only saw #1.