API failure for team match

This match now can't be be accessed from the API, breaking scripts.  

https://www.chess.com/club/matches/1672221

$ curl https://api.chess.com/pub/match/1672221

{"code":0,"message":"An internal error has occurred. Please contact Chess.com Developer's Forum for further help https://www.chess.com/club/chess-com-developer-community ."}

$ curl -v https://api.chess.com/pub/match/1672221
*   Trying 104.18.138.67:443...
* Connected to api.chess.com (104.18.138.67) port 443 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=chess.com
*  start date: May 29 10:33:32 2025 GMT
*  expire date: Aug 27 11:33:12 2025 GMT
*  subjectAltName: host "api.chess.com" matched cert's "*.chess.com"
*  issuer: C=US; O=Google Trust Services; CN=WE1
*  SSL certificate verify ok.
* using HTTP/2
* h2h3 [:method: GET]
* h2h3 [ath: /pub/match/1672221]
* h2h3 [cheme: https]
* h2h3 [:authority: api.chess.com]
* h2h3 [user-agent: curl/7.88.1]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x55ee0b6bd780)
> GET /pub/match/1672221 HTTP/2
> Host: api.chess.com
> user-agent: curl/7.88.1
> accept: */*
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 404 
< date: Fri, 06 Jun 2025 09:04:11 GMT
< content-type: application/json; charset=utf-8
< content-length: 173
< x-chesscom-matched: pubapi_match_TwirpError
< etag: W/"8b6d437c6abd82c9286a4a94dbe908b3"
< link: <https://api.chess.com/context/Exception.jsonld>;; type="application/ld+json"
< last-modified: Friday, 06-Jun-2025 07:26:17 GMT+0000
< access-control-allow-origin: *
< cache-control: public, max-age=30
< expires: Fri, 06 Jun 2025 09:04:21 GMT
< x-chesscom-meta: lean=cached
< x-chesscom-request-id-lb: 5e003dc40eb39f4efb8ec22f4730c4f3
< x-chesscom-request-id-cdn: 94b6bd289a2435ca-DFW
< x-chesscom-servedby: 36
< strict-transport-security: max-age=63072000; includeSubDomains; preload
< cf-cache-status: HIT
< age: 20
< set-cookie: __cf_bm=ASKTUjLdBfhwDQL7wStKhSk393N.gtMM8FBl4kKweC0-1749200651-1.0.1.1-Z0xZ3yCOgIi4sOjy7DIwaU2CHWzNk9XFct.sl62N4cyyLDPQ4J_jRdN5fzLdFku.ttT6Xi0e3pcY6ShdwHQn2u2akB5rtcYibvOnHhqb69NIh5CzikDQKwE0JInW3XO5; path=/; expires=Fri, 06-Jun-25 09:34:11 GMT; domain=.chess.com; HttpOnly; Secure; SameSite=None
< report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=N%2FYd6AZlSqzmyakJ1BdvOj7J8BtW0HSryEYov7rbsyzqbxfwqgP1kNzMjdyEj8c%2BI9eC%2FRtxI1tKmx8KC%2B26VeR2%2Bmh8tffkOI6EJhmafeos7Z0K5yhdgKN7PpjzmU8%3D"}],"group":"cf-nel","max_age":604800}
< nel: {"success_fraction":1,"report_to":"cf-nel","max_age":604800}
< server: cloudflare
< cf-ray: 94b6bda83991f65f-LHR
< alt-svc: h3=":443"; ma=86400
< 
* Connection #0 to host api.chess.com left intact
{"code":0,"message":"An internal error has occurred. Please contact Chess.com Developer's Forum for further help https://www.chess.com/club/chess-com-developer-community ."}

As a minor gripe, I don't see how anyone here in the 'developer community' would be able to help (contrary to the error message) when this is clearly a backend failure in chess.com

is that code?

I have a script which hits the same endpoint https://api.chess.com/pub/match/1672221.

I'm using 'curl' above to provide away for anybody to reproduce the problem without needing my code.

This is common enough although I haven't encountered a broken match endpoint for a few months now but the usual advice is to be patient and the endpoint will probably correct itself.

* Don't you just love those 'auto-emojis' that the post-editor inserts for you?

Or NOT!

Maintenance mode seems to mean we will ignore errors as only a very small percentage of the users are needing them.. I have been tracking a member game archive error for 4 days now. No action.

This one may correct itself at the next 12/24 hour update. That has been seen before.

But have you noticed that things have been much better recently when it comes to match endpoints?

There was a period when I was posting problems here every few days but I haven't needed to for a few months - had to search back to March to find any reports....

https://www.chess.com/clubs/forum/view/errors-in-daily-match-endpoint#comment-112427002

It galls me to admit that something has actually improved on this site but I think it has.

True. Haven't had many problems recently. And the ongoing one I have is becasue of the games archive size I think

This particular match is accessible from the club matches endpoint, but not from the direct matches endpoint. I'll code around it and wait for it to magically fix itself. Thanks

A lot of the 'finicky' endpoints - aka ones that work some days but not others - are probably going to remain that way. It's not typical API behavior, but it is what it is, and I'm guessing the chesscom servers are not configured with the resources it needs. Which is funny because as a live service, an API would be like 0.1% of the hit, but I digress. Anyway, I'm looking forward to the day where the devs put (not that much) money towards an upgraded API. Until then? Calls Calls Calls until it finally works LOL (and TBF it works currently for my uses).

Yuh, it's working now. Thanks