A special Thank You to the Data for Azeroth and All The Things communities - these dedicated collectors have worked tirelessly to bring these bugs to light and attempt to have them fixed for the sake of all collectors. This information has been painstakingly compiled over several years.
If you're interested in joining their Collector Communities, click the Discord links above!
First of All - What's an API?
These bugs aren't easy ones to nail down - and in fact, many players won't even know the basics of why something is wrong in the first place. Many of them trace back to WoW's API, which is the game data that Blizzard allows players to access and is commonly used for creating addons and macro scripts. Many players don't realize that many of the most popular addons they use and depend on on a daily basis exist because Blizzard allows us to use this API freely - and that's why, when something is found to be bugged within it, it can be a big deal. Collectors use the web API, which is slightly different than the in-game API commonly used for addons, but on a technical surface level, they're close to the same thing.
For now, these bugs really only affect collector spaces, but that doesn't mean that somewhere down the line, the interactions won't affect other addons and macro scripts as well. To be clear, this isn't to sound ungrateful - Collectors know that Blizzard giving us this information in the first place is significantly more than most other games have or ever will give to their playerbase - but with continued focus on collecting and more "stuff" being added every patch for Collectors, some of these previously-innocuous bugs have become more and more frustrating for the playerbase.
Character Profiles - Where's My Recipes?
One of the most disruptive bugs for Collectors involves sections that are entirely missing from character profiles. The brunt of API information used on tracking sites or addons such as Data for Azeroth (DfA) or All The Things (ATT) are pulled from these profiles, and this can track dozens of things - from reputations, to achievements, to profession recipes, and more.
Some of these issues are small - for instance, the Marasmius Reputation from the Night Fae Shadowlands covenant is missing - but others are significantly larger in scale. Case in point: Pandaria Cooking Recipes. Data for Azeroth highlights dozens of Pandaria Cooking recipes that simply don't exist in the API, even though every other Cooking recipe in the game is reported completely normally. It's very likely that this is because Pandaria recipes are an oddity among the Profession, with several sub-sections to "learn" as if they were specializations, but it's difficult for anyone but Blizzard to know for sure. This isn't a new issue, either: the earliest known report of this API bug was on the forums over five years ago.
The list of things associated with the character profiles bug is gigantic - whether you're looking at Pandaria cooking recipes, Vulpera Bag of Tricks unlocks, Soulshapes and Crittershapes, looted Treasures, and more, this is easily one of the largest difficulties for Collectors to tackle to track what they have in their hoards of goodies.
Transmog - Why'd I Lose Appearances?
Most players don't worry too much about recipes - but everyone worries about Transmog. A year ago, Blizzard finally added API support for Transmog appearances, and Collectors couldn't have been happier; this was one of the most sought-after API additions (even though ideally, everything collectible such as Drake Manuscripts, Garrison followers, Druid and Warlock pets and transformations, and more would all have API support as well). Unfortunately, this has been a bit of a double-edged sword: the current Transmog API frequently returns incorrect information, and it's been difficult to untangle why.
Currently, the Transmog API updates each time a character logs out; however, it will regularly give the "wrong" data in that update. This makes it seem as though players have "lost" appearances, or didn't earn them properly, causing general confusion and frustration with the system. It's possible to soft reset the API and temporarily fix it by exiting game and restarting, but unless that's done after every character logout, the issue persists.
Blizzard knows that Transmog is a drastically important feature for players - Ion even referenced it during the Systems panel at Gamescom 2025:
While Transmog is going through new feature iterations heading into Midnight, now is a perfect time to tackle this API bug and make tracking easier for all. While we're at it, tracking appearances by source would be a great addition, too!
Why Does This Matter?
For many, collecting of all kinds is the true endgame of World of Warcraft. Whether you're a hardcore DfA Leaderboard topper or just someone who enjoys collecting Transmog, collecting has become as integral to WoW as Dungeons and Raids. Imagine if someone went into a Mythic+ Dungeon and after completing it, was told that Dungeon doesn't count because Blizzard didn't code in the ability for it to give score - that's equivalent to several of these bugs, and truly hampers the collecting experience.
More and more Collector-focused content is on the horizon, and soon, Legion Remix will be here - arguably the biggest Collector event outside of this summer's incredibly successful Collector's Bounty. There are dozens more, uniquely involved bugs with the API as well, but even one or two fixes would be incredibly helpful for those whose passion is tracking completion within WoW. With so many new achievements, mounts, transmogs, and previously unobtainable items returning for a veritable collect-a-thon, it would be a huge win for not just the Collector community but all players if some of these bugs could be fixed before even more content is made available.
