Creature Display Media endpoint bugs

API Bug Report
1

It appears the Creature Display Media endpoint (retail) is now returning only one asset instead of the 3 available variants.

Here is a sample (default API doc creature):
https://{region}.api.blizzard.com/data/wow/media/creature-display/38?namespace=static-us&access_token=

{
  "_links": {
    "self": {
      "href": "https://us.api.blizzard.com/data/wow/media/creature-display/38?namespace=static-8.3.0_32861-us"
    }
  },
  "assets": [
    {
      "key": "zoom",
      "value": "https://render-us.worldofwarcraft.com/npcs/zoom/creature-display-38.jpg"
    }
  ]
}

It used to be like this:

{
  "_links": {
    "self": {
      "href": "https://us.api.blizzard.com/data/wow/media/creature-display/38?namespace=static-8.3.0_32861-us"
    }
  },
  "assets": [
    {
      "key": "portrait",
      "value": "https://render-us.worldofwarcraft.com/npcs/portrait/creature-display-38.jpg"
    },
    {
      "key": "rotate",
      "value": "https://render-us.worldofwarcraft.com/npcs/rotate/creature-display-38.jpg"
    },
    {
      "key": "zoom",
      "value": "https://render-us.worldofwarcraft.com/npcs/zoom/creature-display-38.jpg"
    }
  ]
}

For the classic version the endpoint is still returning 3 assets, however the image urls are returning a XML document reporting error 403.

2

Thanks for the report Schiller!

We’ve confirmed on our end here that the removal of certain assets is working as intended. We are no longer (and have not for a while) generated the ‘portrait’ and ‘rotate’ assets. Our apologies for not posting proactively about this change.

In regards to the 403 response for Classic API assets, that is something we will need to look into further.

Thanks again.

1 Like
3

This is happening with the pvp tier assets as well:

/icons/56/ui_rankedpvp_01.jpg - for example. (I can’t include the full link…)

Thanks!

4

Thanks Gluttony,

We’ve documented this issue.

1 Like