I’m currently upgrading my app from the old v5 API to the latest Twitch API. The Get Followed Streams endpoint was recently added which I was waiting on. However, the old v5 endpoint contains the “profile_banner” information, while the new equivalent API endpoint does not.

In order to get this information, I would now need to make additional API requests to the Get Users endpoint which also requires an additional user:read:email scope.

I’m requesting this information be added back into the Get Followed Streams endpoint so I don’t have to make additional API requests, and not have to force the users of my app to authorize an additional scope.

EDIT: The additional scope is only required if I need email information, which I do not.

Thank you.

Currently the Get Clip endpoint (/clips) is really plain, and not in a really good way. If we could make more complex queries, that would reduce the number of requests we need to make; therefore, less load on Twitch API itself. If I want 50 English clips from the top clips of a single game, let's say League of Legends, I will have to make 3 requests, ignore those that aren't English, and finally list the top 50. But if I can query a game's top clips, AND the language, I can get those 50 clips all in one request. Adding even more optional parameters can help developers get more precisely what they want, in less requests. Win-win situation for both, developers and Twitch API's load.

An update on Jan 31, 2019 gave channel moderators the ability to add comments to users within chat. There is currently no way to use the API to be able to set or retrieve comments for users in chat.

This should be available to the broadcaster and all moderators within a channel.

To add a mod comment to a user, the endpoint could take the following data as inputs:
- User: {user's name}
- Moderator: {mod's name}
- Broadcaster: {broadcaster's name}
- Comment: {comment to be applied}

On success, this would return the following:
- Success: {true}
- date: {date}
- User: {user's name}
- Moderator: {mod's name}
- Broadcaster: {broadcaster's name}
- Comment: {comment applied}

To retrieve mod comments of a user, the endpoint could take the following data as inputs:
- User: {user's name}
- Moderator: {mod's name (optional)}
- Broadcaster: {broadcaster's name}
- date: {date of comment (optional)}
- date range upper: {upper limit of date range (optional)}
- date range lower: {lower limit of date range (optional)}

On success, this would return the following for each comment:
- Success: {true}
- date: {date}
- User: {user's name}
- Moderator: {mod's name}
- Broadcaster: {broadcaster's name}
- Comment: {comment applied}

So lately, one of the top streamed content(from what I've seen) is streamers reacting to YouTube videos. What if you could do business with YouTube to have it when Streamers watch these videos, the viewer count from the stream is contributed towards that 1 view from the streamer. Also maybe you could imbed some way to have an Ad play on the side that one would've seen if they clicked on the video themselves.

Then again, idk all of the legal stuff and such that would have to take place. Also it's probably way more complex to have done than I had imagined in my head haha.

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.

Given the fact that Twitch had to take down the follow/unfollow api's due to bot programs that are out there - my suggestion would be to have an approved set of developers that propose and showcase their applications.

This way Twitch could bring back the follow/unfollow API and any service or developer that was in violation of Twitch's TOS regarding the API could be warned and ultimately have their access and credentials removed.

Twitch Developers could review the logs of which applications were connected with BOT services and immediately shut those down rather then removing the api in its entirety and removing it for those that are using the api to help smaller content creators gain followers and viewers through content.