Legacy Twitch API v5 (i.e. kraken) Shutdown Reminder - February 28, 2022

Update (2022-02-07)
The 24-hour shutdown window has been moved one day to Feb 22 due to Presidents’ Day and reflected below.

This announcement is a reminder that the Legacy Twitch API v5 (i.e. kraken) will be decommissioned on February 28, 2022.

Please refer to the Legacy Twitch API v5 Shutdown Details and Timeline blog post and forum announcement from last year for full details. Critical information regarding dates and migration paths are included below for convenience.

What’s changing?

All endpoints that include the following URLs will be decommissioned later this month.

  • https://api.twitch.tv/kraken/
  • https://api.twitch.tv/extensions/

Note that the “/extensions” endpoints above were migrated to the latest version of the Twitch API. If you are an Extension developer, make sure you are using the Extension endpoints listed in the API reference which all use the https://api.twitch.tv/helix/extensions/ base URL instead of the one above.

When is it happening?

The phased shutdown schedule is included below. During these windows and when permanently removed, requesting these endpoints will return a 404 “This API does not exist” error code and message.

Date Window Length Range (Click to view other timezones)
2022-02-07 1-hour 2022-02-07T19:00:00Z2022-02-07T20:00:00Z
2022-02-09 2-hour 2022-02-09T19:00:00Z2022-02-09T21:00:00Z
2022-02-14 4-hour 2022-02-14T19:00:00Z2022-02-14T23:00:00Z
2022-02-16 6-hour 2022-02-16T19:00:00Z2022-02-17T01:00:00Z
2022-02-22 24-hour 2022-02-22T19:00:00Z2022-02-23T19:00:00Z
2022-02-28 Permanent 2022-02-28T19:00:00Z

What about this specific feature only in V5?

Since the announcement in July, the latest version of the Twitch API included all functionality and data that would be carried over from V5 before the shutdown. UserVoice suggestions for including data in the Twitch API that is currently only available from v5 may be evaluated for future implementation or receive a response if we do not intend to or can no longer supply this information for any reason.

What action needs to be taken?

Refer to the v5 Migration Guide which provides endpoint migration paths and scope equivalence to help ease the migration for your authenticated users.

If you have any questions, please feel free to include them below.