Wow Profile endpoint 404

I’m trying to use the profile endpoint to get a list of the users’ available WoW characters but I keep getting a 404. As I understand it, it’s been migrated to the new profile APIs. I’m trying to hit the endpoint https://eu.api.blizzard.com/profile/<account_id>/wow with the bearer token but I’m always getting 404 responses.

If I try the old Community API endpoint https://eu.api.blizzard.com/wow/user/characters I get a Gateway Timeout.

Any help would be appreciated as I really don’t want to require users to enter every single character name…

As you can see https://eu.api.blizzard.com/profile/<account_id>/wow is listed as IN PROGRESS so it is not available yet.

I just tested and the community endpoint is still working.
Just to be sure, did you obtain the bearer token using the OAuth2 code flow ?

That makes sense on the new API, however I’m still a bit bamboozled as to why the old API gives me an instant Gateway Timeout. I’m using oidc to authenticate and I’m successfully receiving the claims, access_token and id_token. I’m appending the bearer Auth token to all requests and it exists in the headers.


EDIT:
So I’ve found the problem… It doesn’t like the Authorization: bearer <token> header being present on the request. I have to send the access_token as a query parameter without the Authorization header. Seems a bit odd to me - but at least I can code in a workaround…

When this gets migrated to the Profile API, will it work with the Authorization header?

Hi MatteR,

I tested this functionality using the below Curl commands and was able to successfully pull my own account information from the community API, as well as consume dynamic data from the Game Data API.

curl -X GET \
  -H "Authorization: Bearer <CLIENT_CREDENTIALS_TOKEN>" \
  -H "Battlenet-Namespace: dynamic-us" \
  -H "Accept: application/json" \
  "https://us.api.blizzard.com/data/wow/connected-realm/index"

curl -X GET \
  -H "Authorization: Bearer <CODE_AUTHORIZATION_TOKEN>" \
  -H "Accept: application/json" \
  "https://us.api.blizzard.com/wow/user/characters"

My only recommendation at this time is to try and specify Bearer with a capital B, other than that I do not see any difference between my successful test and the information you’ve provided.

Please let us know if this helps.

Thanks

1 Like

Hi Maguthul,

Thank you for your reply - sorry for the late response, I’d put the project down for a while with the current climate…

I’ve just come back to this and I still can’t seem to access the eu endpoints using the Bearer token.

https://eu.api.blizzard.com/profile/user/wow?namespace=profile-eu&locale=en_US&access_token=ACCESS_TOKEN

This seems to work okay if I give it the access token, however if I try and access it with a Bearer token in the Authorization header I still get the 504 Gateway Timeout. I’ve tried both the above URL and https://eu.api.blizzard.com/wow/user/characters in case that makes a difference but I get the same response every time.