There needs to be an API that allows for the return of channal analytics.
This would have the reqiured query parameters of: broadcaster_id

Only stating the broadcaster_id could return the following results:
- Average viewers
- Total views
- Average new followers per stream
- Total followers
- Average subscribers per stream
- Total subscribers
- Average minutes watched per stream
- Total minutes watched

It could also return:
- Best performing catagories
- Best performing tags

There would idealy also be some optional query parameters: start-date, end-date, time.

Adding the optional query parameters would also add the result:
- Start date
- End date
- Period

Hey. I know that people are requesting API for Channel Points. But I came up with better and easier idea.

When streamer creates new reward in dashboard, there should be option to "run a link" in background after reward is redeemed. This type of button will trigger bot with GET-request and bot will run specific action.

Why I think this approach is better than API:
1. No API on Twitch side, obviosly.
2. Bots won't be abble to control Channel Points directly.
3. This will work with any bot who will support this kind of triggers.
4. Easier to use and understand for regular users. Bots developers could design this as "to run this action paste this link in your reward". This sounds pretty easy.
5. Gonna be pretty easy to exclude failed requests for Twitch. You just check if requested link returned: {response: success} or something like that. If it returned something like {error: "Requested video have not enough views."} then you just show this error to viewer and do not take his Channel Points.

Possabilities here are endless. Viewers will be able to request songs with Channel Points, run some sounds and animations on stream, play mini-games, change color of lights in streamer's room, etc.

Currently, it is easy to tell if a user that sent a message in a streamer’s channel is a subscriber, VIP, or moderator of that channel. However, there is no way to tell if that user is a follower of the channel.

With the rise of hate raids and malicious messages, I want to ensure that if a streamer is using a chat box overlay, that they have the option to only let messages from followers appear. Malicious users usually don’t follow the channel, and so this will prevent their messages from appearing on stream.

I do understand that this would be a temporary measure at best, because eventually they might catch on (if they even notice) and start following before sending their message. It is still worth doing. It will help.

I also understand that follower-only mode exists. But that is detrimental to gaining new chatters, and it’s easy enough for malicious users to follow once they realize that the channel is on follower-only mode and then send their message. With a follow tag, malicious users may not even realize that their message didn’t show up in the overlay, since they’re usually there to listen to the streamer’s reaction instead. This can ensure that most malicious messages will not show up in clips or VODs.

In the new badge-related endpoints, badge objects in returned sets contain only their IDs and URLs, which compared to the only existing alternative (undocumented badges.twitch.tv endpoint announced in twitchdev forums[1]) isn't enough for things like custom chat clients that are very popular among many Twitch users.
Ever since that undocumented endpoint came to existence, we've been using it in our chat client and would at least need "description" and "title" properties that are present in badges.twitch.tv to display information about badges properly and replicate webchat's behavior. I believe both APIs use the same internal data (at least for Global Badges) and if that's possible please include more information about badges in the Helix endpoint if possible, thanks!

[1] https://discuss.dev.twitch.tv/t/beta-badge-api/6388

The addition of the Emote Library that is coming soon is a fantastic addition, this is great for solving the issue of disparity between partners and affiliates on emote variety, without undermining the parner program and is a fantastic compromise.

I would like to suggest the addition to the Twitch API to allow for enabling and disabling of active emotes from the Emote library via a privlaged API call from a token with sufficient privlages through oAUTH.

An example of the proposed usecase would be 4 API calls:
-Activate Emote [Params: Emote ID, (Optional: Emote Slot)]
-Deactivate Emote by ID [Params: Emote ID]
-Deactivate Emote by Slot [Params: Emote Slot]
-Replace Emote by ID [Params: Emote ID to Find in active emotes, Emote ID to replace with if Param 1 ID is found in active emotes]

• Activate Emote would add an emote from the emote library by specified ID to the first free slot on the channel's active emotes, or if specified would overwrite an emote in the specified slot.

• Deactivate Emote by ID would remove an emote from the active emotes by specified ID if present in any current slot, if emote ID not found, would do nothing or respond with an Error code.

• Deactivate Emote by Slot would deactivate any active emote found in a specified active emote slot, If slot is already clear, would do nothing or respond with an Error code.

• Replace by Emote ID would search active emotes in slots for a specified emote ID, if found the slot containing the found result would be cleared and then a emote from the emote library specified by ID would be activated to the specified slot.

Programatic access to these functions would allow for great viewer interaction by the creation of immersive experiences allowing viewers to use channel points or other events monitored for via IRC or the pubsub API, to trigger changes to active emotes without disrupting the viewing experience by requiring human intervention by the streamer or another user with privlages to swap emotes.
This would also facilitate the ability for channels that play a few different games or perhaps playthroughs such as variety streams to increase their appeal by creating emotes that are themed around current games or ongoing themed streams, which can then be automatically swapped in and out via the twitch API.

This is an amazing addition you've come up with here for the emote library and I would love to see this included programatically in the API for Follower Emotes, Subscriber Emotes and Bit Emotes ideally, but at the very least, subscriber emotes.