?????
Is this an anomaly? (Problem solved)

I have similar issues with returns for team names which contain extended character set values.
They return a null string instead of an error code. It's a flaw in the API endpoint return I think.

I led myself up the garden path on this one because the club admins hadn't bothered to let me know their club's name had changed (they probably didn't think it would affect anything) and I assumed the very unusual font (/typeface?) of the original had caused the site to alter the name field in the match endpoint(s).

I have similar issues with returns for team names which contain extended character set values.
They return a null string instead of an error code. It's a flaw in the API endpoint return I think.
Haven't encountered that and quite a few of the clubs I deal with have non-ASCII type names:-
NAMASTÉ
Дружба
⇚✯УРАЛ✯URAL✯⇛
Захід
You mean strings like that? Had a problem at the beginning of this year when the club I confused myself over (𝕂ℕ𝕀𝔾ℍ𝕋𝕊 𝕆𝔽 ℍ𝔼𝔸ℝ𝕋𝕊) entered my league for the first time. The version of Python I was using (3.7 I think) couldn't handle that particular font. I upgraded to 3.9 and all was fine.
I can't remember - what language are you working in?

Using VBA in MS office. But that wasn't the problem. It was that some endpoints containing UTF chars don't send back any data. Just null string.
We had a forum about it at the begining of the year.
https://www.chess.com/clubs/forum/view/bug-in-team-matches-endpoint
It's not too bad to get around.

I'd forgotten about that bug. Not sure if the site is getting better but I don't get the endpoint request failures that I used to.
I can't remember the last time I failed to obtain the endpoint I wanted.
Problem solved - the admins of a club taking part in a league I help run hadn't mentioned that their club's name had changed.
I thought there was a problem with one of the endpoints.