There are still a lot of Classic API endpoints not working and I found out this is the status since many many months. Did Blizzard say anything about this issue in the past?
Following API endpoints work for me:
Auction House Index
Auctions
Connected Realms Index
Connected Realm
Connected Realms Search
Creature Search
Item Search
Media Search
PvP Regional Season Index
Realms Index
Realm
Realm Search
Regions Index
Region
Following API endpoints do NOT work for me:
Creature Families Index
Creature Family
Creature Types Index
Creature Type
Creature
Creature Display Media
Creature Family Media
Guild Crest Components Index
Guild Crest Border Media
Guild Crest Emblem Media
Item Classes Index
Item Class
Item Subclass
Item
Item Media
Playable Classes Index
Playable Class
Playable Class Media
Playable Races Index
Playable Race
Power Types Index
Power Type
PvP Seasons Index
PvP Season
PvP Region Index
PvP Regional Season
PvP Leaderboards Index
PvP Leaderboard
PvP Rewards Index
WoW Token Index (CN)
Apologies for the inconvenience and the late response. It appears that the static-classic-xx namespace aliases were not properly updated with patch 3.4.3 as intended. While this is unfortunate, it was more impactful as the old 3.4.2 namespaces that the aliases were referencing appear to have been removed at some point (which is why they were returning 404s).
We will try to watch this more closely in the future, but if you are ever having issues using the aliases, it is also possible to access the namespaces by build directly.
e.g. static-3.4.3_51505-classic-us
This may also be helpful to compare or reference older static APIs if that is of value.
Also, it may not be the most intuitive method, but recently updated profile or dynamic namespace APIs reference/link the static namespaces by build rather than using the alias. In this way it is possible to locate the latest namespace if desired.
There are a few APIs in which localization strings are collapsed and only strings for en_US are present. We understand that this is not ideal, but because of the potential size of some of these profile documents and number of referenced strings, we are unable to include localizations. In these cases, localization strings from the static references must be retrieved (which should always be linked from the profile APIs).
I know this affects the Profile achievements, quests, professions, and encounters (dungeons/raids) APIs off the top of my head.
As you said, the Achievement API handled it that way.
We would like to ask you to ensure that the APIs below operate normally. thank you
You said it might work if you use the latest namespace instead of the alias namespace, but I couldn’t find a namespace that would work.
Profile Character Appearance
PvP Seasons Index
PvP Season
PvP Region Index
PvP Regional Season
PvP Leaderboards Index
PvP Leaderboard
PvP Rewards Index