Twitch API
GET /helix/hypetrain/events endpoint removal
Stopped workingSubscribe to Twitch APIShare
Calls to GET /helix/hypetrain/events on Twitch API stopped working on December 4, 2025.
Calls it hits
GET /helix/hypetrain/events
What to use instead of these calls
Use Get Hype Train Status (GET /helix/hypetrain/status) instead.
In Twitch API's words
“Get Hype Train Events” API endpoint and V1 of the Hype Train EventSub subscription types are decommissioned.
Facts
- API
- Twitch API
api.twitch.tv - Kind
- Endpoint removal
- Takes effect
- December 4, 2025
- 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/hypetrain/events on Twitch API stopped working on December 4, 2025.
What happens to calls after December 4, 2025?
They have failed since December 4, 2025.
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 7
-
/helix/entitlements/codesEndpoint removal Stopped working -
PUT /helix/streams/tagsEndpoint removal Stopped working -
GET /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 -
No date
POST /helix/moderation/automod/statusParameter removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.