[Era] Guild and Guild Roster API no longer works

Do you have an example you could share that I could use to replicate what you are experiencing?


I had a look at the documentation and did notice that using the web-interface “try it” option also resulted in 401 Unauthorized. For example, using the /data/wow/connected-realm/index endpoint from Game Data APIs.

Following the advice from the linked posters above, I tried using a bearer token and was still getting the same issues, until I noticed that namespace is a required parameter and can be given as a Battlenet-Namespace header. Here’s a working example using NodeJS with the Axios package that may prove useful in your own troubleshooting:

const axios = require('axios');
const url = YOUR_URL;
const token YOUR_ACCESS_TOKEN;

axios.get(url, {
  headers: {
    'Authorization': `Bearer ${token}`,
    'Region': 'us',
    'Battlenet-Namespace': 'dynamic-us',
  }
})
.then(resp => {
  console.log(resp.data);
})
.catch(e => {
  console.log('Error with request: ', e);
});

Obviously, you’ll want to replace YOUR_URL and YOUR_ACCESS_TOKEN with the relevant values. In this case, I used https://us.api.blizzard.com/data/wow/connected-realm/index as the URL, and for my access token, I just generated it using the curl call from the documentation:

curl -u {client_id}:{client_secret} -d grant_type=client_credentials https:oauth.battle.net/token

Replacing {client_id} and {client_secret} with the values from an API Access Client from the developer portal (https://develop.battle.net/access/clients).

Of potentially interesting note, adding the required headers to a curl request also seems to give the expected results…

curl -i -H "Authorization: Bearer YOUR_ACCESS_TOKEN" -H "Region: us" -H "Battlenet-Namespace: dynamic-us" -X GET https://us.api.blizzard.com/data/wow/connected-realm/index

# Additional Examples: 

## get hunter pets
curl -i -H "Authorization: Bearer YOUR_ACCESS_TOKEN" -H "Region: us" -H "Battlenet-Namespace:  profile-classic-us" -X GET https://us.api.blizzard.com/profile/wow/character/faerlina/snipy/hunter-pets

## get character equipment
curl -i -H "Authorization: Bearer YOUR_ACCESS_TOKEN" -H "Region: us" -H "Battlenet-Namespace: profile-classic-us" -X GET https://us.api.blizzard.com/profile/wow/character/faerlina/snipy/equipment

## specifying Era using classic1x
curl -i -H "Authorization: Bearer YOUR_ACCESS_TOKEN" -H "Region: us" -H "Battlenet-Namespace: profile-classic1x-us" -X GET https://us.api.blizzard.com/profile/wow/character/whitemane/astralarya/equipment

1 Like

Try:

curl -i -H "Authorization: Bearer YOUR_AUTH_TOKEN" -H "Region: us" -H "Battlenet-Namespace: profile-classic1x-us" -X GET https://us.api.blizzard.com/data/wow/guild/whitemane/not-prepared

Result:

HTTP/1.1 403 Forbidden
Date: Tue, 05 Nov 2024 19:08:05 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
vary: accept-encoding
blizzard-token-expires: 2024-11-06T10:01:27.832Z
x-trace-traceid: d309f9e7-1819-3e8d-8c0a-b236243a1253
x-trace-spanid: 1801b703-fe3a-34e6-e6e1-fa164d6d41f5
x-trace-parentspanid: 1801b703-fe3a-34b6-e6e1-fa164d6d41f5
x-frame-options: SAMEORIGIN
X-Content-Type-Options: nosniff
server: blizzard

{"code":403,"type":"BLZWEBAPI00000403","detail":"Forbidden"}
2 Likes

Playing around with this a little, it seems that it will return a 403 for guilds that exist, and a 404 for ones it cannot find, and that this behavior is consistent for Classic Era and Classic (Progression), but inconsistent with how this API works for Retail, which gives the expected results, e.g.

curl -i -H "Authorization: Bearer YOUR_ACCESS_TOKEN" -H "Region: us" -H "Battlenet-Namespace: profile-us" -X GET https://us.api.blizzard.com/data/wow/guild/tichondrius/the-move

Basically, all this just to say I was able to reproduce your issue.

1 Like

Please fix this Blizzard, as we are relying on this API for managing our guild in Classic Era

3 Likes

please fix this blizz

2 Likes

Updating that this is still an ongoing issue.

Still an issue…

1 Like

Our guild uses this API for a non-GDKP loot system, RRobin. With GDKP being banned on fresh Classic, this API is going to be more important than ever. Blizzard, please fix this :worried:

Blizzard please fix

1 Like

Blizzard please fix

1 Like