403 / 404 - Classic & Classic1x

API Discussion
1

I’ve noticed that recently I’m getting either 403 or 404 for some (not all) endpoints in the classic api, for both namespaces.

The Account Profile Summary (/profile/user/wow) endpoint works fine and I get all my characters for both Classic and Classicx1 namespaces.

An example where I get 404 is the Character Apperance Summary (/profile/wow/character/{realmSlug}/{characterName}/appearance). Which is strange when the character does exist.

I sometimes get 403 with the Protected Character Profile Summary (/profile/user/wow/protected-character/{realmId}-{characterId}) Which makes no sense since I’m able to get the Account Profile Summary which requires the wow-profile scope, the same as this endpoint.

Edit: Should mention that I’ve only tried it with EU. I don’t have access to an account on NA.

Is this a know issue? Have Blizzard mentioned anything on why this is happening or when it will be fixed?

2

Me too!
The chars exists they get shown under

Account Profile Summary
/profile/user/wow

But not if i try to grab the equipment. It results in

{
  "code": 404,
  "type": "BLZWEBAPI00000404",
  "detail": "Not Found"
}

It is not the API endpoint itself. Its the data… I am able to find older character names

eu
razorfen
syreana
profile-classic1x-eu
de_DE

Works with a 200 okay

But for example my char “filgaja” I created 9 hours ago do not.
I think they simply fetch era classic data less frequently? or the api updater crashed?

I tried with different chars with different results.

3

Maybe. I tried again an I can get the unprotected route for a character and it returns 200. But when I try to get the protected route for the same character, it returns 403. Which is again strange, since the protected route requires the wow.profile scope, which is the same as the Profile Summary endpoint.

So I still think there’s something wrong with the API.

4

I can confirm I have the same problem using the /profile/user/wow/protected-character/{realmId}-{characterId}?namespace=profile-classic1x-eu endpoint. Also on EU, haven’t tested US.