query parameter access_token → behaviour change
Blizzard Battle.net API
Stopped working
On September 30, 2024, the Blizzard Battle.net API stopped accepting the query parameter access_token. Calls that pass OAuth access tokens via the query parameter fail after this date. It is no longer permissible to provide access tokens through the URL query string.
Calls it hits
query parameter access_token
What to use instead of these calls
Send the token in an Authorization: Bearer {token} header instead of using ?access_token=.
In Blizzard Battle.net API's words
First, it will no longer be permissible to pass OAuth Access Tokens via the URL query string. Instead, these tokens must be included in the HTTP header of the request
Facts
- API
- Blizzard Battle.net API
*.api.blizzard.com - Kind
- Behaviour change
- Announced
- August 9, 2024
- Takes effect
- September 30, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Blizzard Battle.net API's own pages
Questions
When does this change take effect?
Calls to query parameter access_token on Blizzard Battle.net API stopped working on September 30, 2024.
What happens to calls after September 30, 2024?
They have failed since September 30, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.