436 results found

1. Bot auto follow a channel

   With the removal of the Follow Create endpoint.

   A "non moderation bot" can no longer be automatically added to a channel.
   The owner of the bot would have to "login" to the account and manually follow the channel(s) the bot joins.

   A "non moderation" bot doesn't run moderation commands, so giving it "mod" wouldn't make sense. (Which would bypass the follow requirement)

   Please provide a way to "authorise adding a bot to a channel" that will auto follow the bot to the channel. For this purpose

   This could be similar to how Discord does bots, where to add a bot to a server, you need an oAuth flow, and then on compleition of that flow lets the bot in the server.

   So in this example, I login as barrycarlyon I grant the bot access to my channel using scope "bot:allow" this auto follows that bot to my channel.

   So the "follow" is initated from my website and the channel authenticating in.
   And I've authenticated "my bot" to my clientID, and the target channel to my clientID.

   This essentially sets it up, so that the destination channel triggers the follow.

   With the removal of the Follow Create endpoint.

   A "non moderation bot" can no longer be automatically added to a channel.
   The owner of the bot would have to "login" to the account and manually follow the channel(s) the bot joins.

   A "non moderation" bot doesn't run moderation commands, so giving it "mod" wouldn't make sense. (Which would bypass the follow requirement)

   Please provide a way to "authorise adding a bot to a channel" that will auto follow the bot to the channel. For this purpose

   This could be similar to how Discord does bots, where to add a bot… more

   40 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Investigating  ·  14 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. IRC Request: Follow tag to filter out non follower messages

   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.

   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… more

   38 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. API to CRUD panels for streamers

   Including but not limited to.

   • Add new panel
   • Remove Panel
   • Update panel
   • Change order of panels
   37 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. 2FA status in users endpoint (when authing as the user)

   We third party dev's often build tools that assist with moderation actions/services for broadcasters.

   We tell Moderators to enable 2FA, but we have no way to check it.

   It would be useful to block Logins to our tool if 2FA is not enabled. But 2FA data is not surfaced in the API and there's no way to require a User to be 2FA during the login/oAuth loop.

   I'd like to see the users endpoint(s) provide 2FA status.
   I expect this to be behind the user read or openID scopes.

   openID allows email verified. Why not 2fa status (for example)

   Worth noting that Discords floats "mfa_enabled" in it's user API so we have precedent.

   We third party dev's often build tools that assist with moderation actions/services for broadcasters.

   We tell Moderators to enable 2FA, but we have no way to check it.

   It would be useful to block Logins to our tool if 2FA is not enabled. But 2FA data is not surfaced in the API and there's no way to require a User to be 2FA during the login/oAuth loop.

   I'd like to see the users endpoint(s) provide 2FA status.
   I expect this to be behind the user read or openID scopes.

   openID allows email verified. Why not 2fa status (for example)

   Worth… more

   37 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Extend Moderation API to retrieve and set mod comments of a defined user

   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}

   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}… more

   35 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. "Get Users Follows" with follower's account creation date

   The v5 endpoint contains the follower's account creation date, the new endpoint (https://dev.twitch.tv/docs/api/reference#get-users-follows) does not.

   Knowing when a follower created their account is very useful to moderators monitoring recent follows to keep an eye on potentially problematic users (new account could mean a previously banned user returning) or to detect mass follows from bots (which often have a similar account creation date). Monitoring recent follows is especially useful in follow-only chat mode.

   While it is possible to get the account creation date from the "Get Users" endpoint (https://dev.twitch.tv/docs/api/reference#get-users) and then merge it with the follower data, it would be nice if it were in the "Get Users Follows" endpoint as well, which would reduce the amount of API requests required.

   The v5 endpoint contains the follower's account creation date, the new endpoint (https://dev.twitch.tv/docs/api/reference#get-users-follows) does not.

   Knowing when a follower created their account is very useful to moderators monitoring recent follows to keep an eye on potentially problematic users (new account could mean a previously banned user returning) or to detect mass follows from bots (which often have a similar account creation date). Monitoring recent follows is especially useful in follow-only chat mode.

   While it is possible to get the account creation date from the "Get Users" endpoint (https://dev.twitch.tv/docs/api/reference#get-users) and then merge it with the follower data,… more

   33 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Extension webhooks for streamer actions

   For the purposes of GDPR it would be useful to have the following webhooks:

   • When a Streamer installs an extension
   • When a streamer activates an extension
   • When a streamer deactivates an extension
   • When a streamer uninstalls an extension.

   The most important one is the uninstall, it allows us the third party to be notified of an uninstalled.

   The Shopify platform has this with the rule that a third party should, automatically delete all Store (and that stores customer data) 30 days after that hook triggers.

   We need/should do the same, delete any broadcaster, or broadcaster viewer (and subscribers) data 30 days after the uninstall. (The 30 days allow for the broadcaster to reinstall the extension and avoid the caster having to re-setup the extension, when talking about any configuration, and hence the need for the install hook to go hand in hand)

   Activate/deactivate are useful for the purpose of turning on/off any backend services related to the extension, couple that with https://twitch.uservoice.com/forums/310213-developers/suggestions/37563622-live-activated-channels-w-extension-webhook for video extensions to improve accuracy of whose live and who needs backend service support.

   For the purposes of GDPR it would be useful to have the following webhooks:

   • When a Streamer installs an extension
   • When a streamer activates an extension
   • When a streamer deactivates an extension
   • When a streamer uninstalls an extension.

   The most important one is the uninstall, it allows us the third party to be notified of an uninstalled.

   The Shopify platform has this with the rule that a third party should, automatically delete all Store (and that stores customer data) 30 days after that hook triggers.

   We need/should do the same, delete any broadcaster, or broadcaster viewer (and subscribers) data 30… more

   33 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Latest cheers API endpoint

   Add an endpoint the returns a list of the latest cheers to a channel. The list should include: username, bits, message and date-time.

   31 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Add endpoints to set and retrieve moderator comments for a user

   See https://blog.twitch.tv/channel-moderation-tools-in-chat-4188af21dbf9 for details.

   29 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Expose Games/Chapters on the Videos API

    There's currently no way to view the games/chapters on a video. This would be very useful for an application I'm building

    28 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Manage Roles via the API

    It shouldn't be required for manage roles such as mod/vip via the chat

    It shouldn't be required to manage editor/mod/vip via the roles manager

    it would be useful for automation/third party management to be able to manage roles via the API

    28 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    5 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close
    Deferred  ·  AdminJon Bulava (Developer Relations, Twitch) responded

    Currently not a top priority, but we are interested in your use cases for this functionality to be considered at a later time. Please include more information in the comments as to how and why this would be useful.

12. Webhook for commercials

    Please provide a webhook so that authorised tools can collect Commercial status when an ad is run not via the Start Commercial API endpoint (ie Via chat or another authorised user)

    So tool A will know not to try and run ads because user Fred just did

    And Tool A doesn't want to run ads after the "retry_after" period as Fred ran the ads 20 minutes early. so we'd want to reset the start point to when Fred ran ads. For say when Tool A runs ads one per hour

    For example

    27 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Subscriber start date

    Add subscriber start date to get broadcaster subscriptions endpoint

    25 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Add subscriber only status to Streams API endpoint.

    Right now there is no official way (there is an undocumented endpoint) to determine whether a stream is sub only or not. Subscriber only status prohibits a lot of people from interacting with the stream, so it'd make sense for applications to be aware of such a state.

    25 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Offer a way to better handle app authorization on password reset

    One of the annoyances of the current authorization system is that whenever the broadcaster change their password, they need to reauthorize all apps as well, so developers need to have a way of warning the user to reauthorize it, or they will lose access to its features.

    I understand this is a security feature, but it would be good if that could be handled separately, because a lot of times people just want to change password, and not revoke auth for third party apps

    24 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Indicate on GetUser endpoint if he/she allows raids

    A streamer can configure if he/she allows to send a raid to his/her channel or not. But this information can't get using twitch api endpoint. The only way is trying to send a raid, and check if any error is returned or not.

    Add this information directly in twitch API can helpful to select a streamer to send a raid.

    22 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Allow Channel Editors to use Helix Raids API

    With the new Raids API, it should mirror IRC where channel editors can trigger raid/unraid. Currently, this is not supported (need broadcaster user access token). Until this functionality is added, I will not be migrating to Helix Raids

    22 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Include emote artist in the Get Emote Sets endpoint

    The API does not include any attribution info at the moment, it would be nice if we could get the artist's username and id with the emote data :)

    22 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Stories: Upload API

    Please provide an API to upload Stories so that the channel editor using an external tool can complete creating a story and upload it using a suitable tool, as apposed to the Twitch Dashboard.

    This could be an after effects/premiere plugin for example that auto uploads after rendering

    20 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Extend the "ban user" endpoint to accept "login" as an alternative to the already existing "user_id"

    Today when you're using chat you can just enter /ban user and the user will be banned, and the same is true for the IRC command, you can ban just by their username. It would be good if the ban endpoint would follow the same pattern.

    The use case for that is that I have a tool to mass-ban multiple users on multiple channels at the same time (I mod quite a lot of channels, so this streamlines this process), and I decided to migrate from the IRC API to the helix API, but because of it just accepting the user_id, now I have to do an additional request to get their ids first (or multiple requests, if there are more than 100 users), which is inconvenient, but the real problem is:

    • I can't ban users which are suspended/deactivated anymore cause I don't know their id, and the get users endpoint just returns that the user does not exist when they are suspended/deactivated (even though they do exist, and could be unsuspended/deactivated at any time). Even though they are suspended, I still want to ban them, as I can't know if the suspension is temporary or permanent, or if the user will just reactivate the account sometime later.

    I feel like being able to just pass the login to that endpoint would make the whole process a lot easier and faster (and also, it would save a few requests to get their ids)

    Today when you're using chat you can just enter /ban user and the user will be banned, and the same is true for the IRC command, you can ban just by their username. It would be good if the ban endpoint would follow the same pattern.

    The use case for that is that I have a tool to mass-ban multiple users on multiple channels at the same time (I mod quite a lot of channels, so this streamlines this process), and I decided to migrate from the IRC API to the helix API, but because of it just accepting the… more

    20 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Deferred  ·  0 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close