GET /helix/streams/tags → endpoint removal
Twitch API
Stopped working
On July 13, 2023, Twitch removed the GET /helix/streams/tags endpoint. Requests sent to this endpoint now fail, as the provider began returning a 410 response on that date.
Calls it hits
GET /helix/streams/tags
What to use instead of these calls
Use the customizable tags field of Get Channel Information and Modify Channel Information instead.
In Twitch API's words
These endpoints will return a 410 response on July 13, 2023
Facts
- API
- Twitch API
api.twitch.tv - Kind
- Endpoint removal
- Announced
- February 28, 2023
- Takes effect
- July 13, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Twitch API's own pages
Questions
When does this change take effect?
Calls to GET /helix/streams/tags on Twitch API stopped working on July 13, 2023.
What happens to calls after July 13, 2023?
They have failed since July 13, 2023.
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.
More from Twitch API 6
-
/helix/entitlements/codesEndpoint removal Stopped working -
PUT /helix/streams/tagsEndpoint removal Stopped working -
GET /helix/tags/streamsEndpoint removal Stopped working -
GET /helix/soundtrack/*Endpoint removal Stopped working -
GET /helix/users/followsEndpoint removal Stopped working -
GET /helix/hypetrain/eventsEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.