Update (2023-02-10): A more readable timeline has been added below regarding when to expect changes to the legacy tags API endpoints.
Last year, Twitch announced customizable tags to improve how streamers describe themselves and their content, and to help viewers find communities they’re interested in. And now the Twitch API has been updated to support the latest tagging functionality. Below, you will find further information regarding our recent documentation updates as well as the deprecation timeline for legacy tags.
Unlike the legacy tags returned in the Twitch API, the new customizable tags do not have tag IDs and are not localized into multiple languages. Because of these differences between the older tags and new customizable tags, we’ve added a new
tags array to the objects in the following Twitch API endpoints used to retrieve stream or channel information:
We have also updated the Modify Channel Information Twitch API endpoint to include customizable tags in the request body to set tags for a channel.
Customizable tags are replacing the old tag format. Because we’ve added the ability to get and set customizable tags via “Get Channel Information” and “Modify Channel Information,” the legacy tags endpoints and data will be phased out of the Twitch API according to the following timeline.
- February 13, 2023
- The legacy
tag_idsarray in API responses that provides the older tag format will begin returning an empty array. This array can be found in Get Streams, Get Followed Streams, and Search Channels.
- The legacy
- February 28, 2023
- “Get Stream Tags” and “Get All Stream Tags” will return empty arrays.
- “Replace Stream Tags” will return at 410 response.
- July 13, 2023
- “Get Stream Tags” and “Get All Stream Tags” will return at 410 response.
Developers should also note that a customizable tag localized to the broadcast language has automatically been added since the launch of customizable tags for consistency between the two tagging systems. This automatic behavior will be removed now that customizable tag functionality is available via Modify Channel Info. Therefore, third-party applications should include a language tag in their Modify Channel Info requests if the creator expects a language tag to be present for their stream.
Review the documentation linked above for each endpoint to understand where to find tags in the response.
As always, we appreciate your feedback in UserVoice to help prioritize our third-party developer product features and thanks to Durss for the customizable tags UserVoice suggestion.