Summary
Now that the new Get Hype Train Status API is generally available, we’re deprecating the Get Hype Train Events API. We will withdraw the Get Hype Train Status API and the EventSub Channel Hype Train Begin v1, Channel Hype Train Progress V1, and Channel Hype Train End v1 subscription types on Thursday, December 4, 2025. If your application uses this deprecated Hype Train functionality, you’ll need to migrate your application before this date to avoid disruption.
Developers who are using the Get Hype Train Events Twitch API endpoint (i.e. /helix/hypetrain/events) should migrate to Get Hype Train Status endpoint (i.e. /helix/hypetrain/status) at their convenience prior to the decommission date above. After this date, developers can expect to receive a 410 HTTP response error for the former endpoint.
https://discuss.dev.twitch.com/t/legacy-get-hype-train-events-api-and-eventsub-hype-train-v1-subscription-types-deprecation-and-withdrawal-timeline/64299
Solution
Summary
Now that the new Get Hype Train Status API is generally available, we’re deprecating the Get Hype Train Events API. We will withdraw the Get Hype Train Status API and the EventSub Channel Hype Train Begin v1, Channel Hype Train Progress V1, and Channel Hype Train End v1 subscription types on Thursday, December 4, 2025. If your application uses this deprecated Hype Train functionality, you’ll need to migrate your application before this date to avoid disruption.
Developers who are using the Get Hype Train Events Twitch API endpoint (i.e. /helix/hypetrain/events) should migrate to Get Hype Train Status endpoint (i.e. /helix/hypetrain/status) at their convenience prior to the decommission date above. After this date, developers can expect to receive a 410 HTTP response error for the former endpoint.
https://discuss.dev.twitch.com/t/legacy-get-hype-train-events-api-and-eventsub-hype-train-v1-subscription-types-deprecation-and-withdrawal-timeline/64299
Solution