As it stands currently today, whether you are building a large scale bot to connect to multiple channels, that is always on (think Streamlabs, StreamElements, etc), or a small bot specific for your channel, or perhaps somewhere in between, the only supported way to connect is via the channel name, which is tied directly to the Twitch username.

The problem that is faced is when one of those connected channel's broadcaster decide to change their username, thus changing the channel name as well, since now what the bot is listening for data on is non-existent. The way this is managed today is by utilizing webhooks to listen for user changes, and the moment a username has been updated, the webhook is notified, and the bot must sever the previous connection and establish a new connection to the new username.

What i propose is providing the capability to also allow connections to a channel based on the Broadcaster ID, being a numeric value that never changes over the lifetime of the twitch account's existence. By allowing this capability, an IRC bot could connect in via the ID, and stay connected, regardless of name changes, which saves on resources from both the bot and Twitch's side.

Good thing is that the data needed (i.e. the broadcaster ID) is already available on the helix endpoints for channels and users, so no modifications to the API would be needed!

The changes (from the outside looking in) would entail accepting a numeric based ID for the connect call, then updates to the IRC infrastructure to support it. I'm certain there could be a bit of finesse in how the data is translated to make the footprint minimal.

Overall gains: Ease of IRC bot management, less load on bot, less load on Twitch (no need for webhooks just for username changes)

Specifically talking about:
- Get Channel Information: helix/channels
- Search Channel: helix/search/channels
- Get Users: helix/users

Those endpoints all return data concerning a specific channel, but all of the JSON responses are different and no single endpoint contains all the data you need.

Say I have a user id and want to get the profile picture of that channel, whether it is live and the title of the broadcast.

For the profile picture I have to hit the 'Get Users' endpoint.
For the 'isLive' info I need to hit the 'Search Channels' endpoint, and then find the correct user from the returned search results.
For the title I need to hit the 'Get Channel Information' endpoint.

I would expect all of this information to be available in a single API call like 'Get Channel Information'.

It is quite hard to find clips using https://www.twitch.tv/manager/clips page to find clips and API does not offer nice solutions to make a 3rd party application to replace it.
Here are some examples of API request parameters and some of their possible uses.

curator_id:
- clip creator can find all their own clips
- broadcaster can find and delete all the clips from problematic viewer

vod_id:
- find clip compilation material for the stream

created_at:
- find clip compilation material for the date(and range)
- find throwback clips - "last year this time we did this"

broadcaster_id:
- in combination with others would make the API request more useful

Authenticate a PC across all of your platforms. Example: Twitch Web and Desktop App, Broadcasting software (StreamLabs OBS), etc.

Right now, after re-installing my Windows, I had to request an SMS authentication code for Web, Twitch App Desktop and StreamLabs OBS. Since I had to reset my password (forgot it once again, since I am not allowed to have an Easy password) I have totally requested 3 sms messages. After which I get locked out and I couldn't get a code for the Desktop Twitch App for that period of time, on the same PC.

Authenticating the PC uniquely, without having to authenticate the pc each time when a login has occurred from a new App supporting Twitch Login, would be a lot better UX. Please consider updating your API, cuz I'm pretty sure that's what's handling it. I am even assuming the initial idea is that, but it somehow fails on a Back-end level.

It is useful to know if a streamer is on the home page.

Both from a

• internal (to the channel) statistical standpoint


• as a moderation standpoint (we are on the home page we should up the follow limit to avoid trolls or lower the follow limit to let people chat).

Please provide a way to

• determine if a given channel is on the homepage (by region)


• which slot it is in on that region

And if possible

provide this information has a webhook so we don't have to constantly poll for this information

Additionally we may use it as a way to detect when a sponsored segment (for the streamer) starts/ends easily.