For example, if I try the WoW Guild profile API in the Documentation then the URL it generates is:
https://eu.api.blizzard.com/data/wow/guild/testrealm/testguild?namespace=profile-eu&locale=en_GB&access_token=SOMEVALIDACCESSTOKENVALUE
This returns a 401 Authorization error code because the access token is no longer allowed to be appended to the URL as a parameter. Instead the access token must be hidden in the HTTP header.
This means that ALL the WoW Documentation API’s cannot be Tried, because the Blizzard Battle.net Developer Portal web site does not create valid HTTP requests with the access token in the HTTP header.
Please fix this urgently. The Try It feature of the API Documentation is needed to be able to test how the API’s work, what the JSON results will look like, to be able to do testing and design applications, without having to do laborious coding.
The cut-off date for all users to migrate to putting the access token in the HTTP headers for HTTP requests was September 30th 2024. It is well past time now for Blizzard to upgrade the develop.battle.net web site to conform with that API upgrade also!