701 results found

1. Power Up Pricing

   Power Ups do broadcast via EventSub but we developers have no way to get whatever the pricing is of those power ups on the channel inquestion.

   Provide this information so our activity feed third party equivelents can display the right information and/or allow streamers using third party tooling to estimate their income

   This could also perhaps extend to the core/in built rewards (obtain a channel emote for 24 hours/etc)

   35 votes

   Vote 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

   Submit Rating

2. Anything that relates to or generates a chat message, include the TMI chat message ID

   Various eventsub types will result in a chat message being generated.

   If that is the case as well as the fragments and raw chat message the resultant TMI message ID should be included.

   Conceptually I can see understand this isn't possible but the UV exists as a request anyway.

   Use cases:

   • Various things need replies to, if replies supported.
   • Being able to do moderation on JUST say, cheers or redeems (as apposed to the entire chat)

   additionally anything that has a chat message generated the relevant eventsub types should use a consistent fragment formats that chat.message uses.

   7 votes

   Vote 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  ·  EventSub  ·  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

   Submit Rating

3. Add timestamp to channel.chat.message

   Add Timestamp when message was sent to channel.chat.message

   Why?
   Including the original timestamp of when a message was sent would be extremely valuable for multiple reasons:

   Improved Debugging – When a server processes a message with delay, having access to the actual sent time makes it much easier to identify and troubleshoot latency issues in the message flow.

   Support for Time-Sensitive Chat Games – Some chat-based games rely on the exact send time of a message to determine whether to process it. In the event of lag, having the original timestamp allows developers to rely on Twitch’s data rather than local server timing, ensuring fair and accurate gameplay.

   This data is already captured by Twitch, so exposing it through the channel.chat.message event should be straightforward to implement.

   Thanks in advance!

   Add Timestamp when message was sent to channel.chat.message

   Why?
   Including the original timestamp of when a message was sent would be extremely valuable for multiple reasons:

   Improved Debugging – When a server processes a message with delay, having access to the actual sent time makes it much easier to identify and troubleshoot latency issues in the message flow.

   Support for Time-Sensitive Chat Games – Some chat-based games rely on the exact send time of a message to determine whether to process it. In the event of lag, having the original timestamp allows developers to rely on Twitch’s data rather than… more

   4 votes

   Vote 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  ·  EventSub  ·  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

   Submit Rating

4. Add contributor to Hype Train Progress V2 Event as it was in Hype Train Progress Event

   The V1 Hype Train Progress Event included the "Last Contribution" data. With a use case of including all participating users in a "Thank You" message (or similar), this information is beneficial.

   Hype Train Progress V2 Event does not include the users who have contributed besides the "Top Contributions". The alternate method I could think of would be to treat all subs and cheers between a "Hype Train Begin" and "Hype Train End" event as contributors, but this also currently negates all users who participated via extensions since those Bit Events are not available. Should those Bit Events become available, I would be willing to use this alternative for my use case (though clearly less convenient).

   In summary, I am interested in a method to thank ALL users who contribute to a hype train, as was possible via the V1 Hype Train Progress Event. Thank you.

   The V1 Hype Train Progress Event included the "Last Contribution" data. With a use case of including all participating users in a "Thank You" message (or similar), this information is beneficial.

   Hype Train Progress V2 Event does not include the users who have contributed besides the "Top Contributions". The alternate method I could think of would be to treat all subs and cheers between a "Hype Train Begin" and "Hype Train End" event as contributors, but this also currently negates all users who participated via extensions since those Bit Events are not available. Should those Bit Events become available, I… more

   2 votes

   Vote 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  ·  EventSub  ·  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

   Submit Rating

5. Restore consistency for custom_reward.id: visible in GraphQL, blocked in Helix

   Currently, custom_reward.id is:

   Publicly visible via unauthenticated GraphQL responses in the Twitch frontend (to anyone with DevTools).

   Blocked in the Helix API unless the request is authenticated as the broadcaster and includes elevated scopes.

   This architectural inconsistency causes confusion and unnecessary friction for developers.

   A well-structured access model should behave consistently:

   If custom_reward.id is public (as its frontend exposure implies), it should be accessible via Helix in a read-only context — no scopes required.

   If it’s private, then it should not appear in frontend GraphQL queries without authentication.

   This is not a feature request.
   This is about fixing a fundamental inconsistency in the platform’s data access model.

   Twitch developers rely on predictable and consistent APIs when building integrations like overlays, bots, or analytics. Forcing them into undocumented workarounds (e.g., scraping) degrades both developer trust and platform integrity.

   Please consider:
   Allowing custom_reward.id to be accessed via Helix in read-only mode, without requiring authentication, or

   Restricting its frontend exposure, if it is meant to be protected.

   If Twitch treats 1st-party and 3rd-party differently, that distinction should still preserve internal consistency. A data field should not be both “public” and “private” depending on which API surface you're looking at.

   Let’s fix this — not because it's convenient, but because it’s the correct architectural behavior.

   Currently, custom_reward.id is:

   Publicly visible via unauthenticated GraphQL responses in the Twitch frontend (to anyone with DevTools).

   Blocked in the Helix API unless the request is authenticated as the broadcaster and includes elevated scopes.

   This architectural inconsistency causes confusion and unnecessary friction for developers.

   A well-structured access model should behave consistently:

   If custom_reward.id is public (as its frontend exposure implies), it should be accessible via Helix in a read-only context — no scopes required.

   If it’s private, then it should not appear in frontend GraphQL queries without authentication.

   This is not a feature request.
   This is about fixing a fundamental… more

   3 votes

   Vote 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

   Submit Rating

6. Improve Error Messages for Send Chat Message

   When switching from IRC to the "Send Chat Message" Helix endpoint in a third party chat client, we noticed that the error messages were less descriptive when compared to some of the NOTICE messages received through IRC.

   • When a user is timed out and attempts to send a message, they get a drop_reason of "You are timed out from talking in the room." (code: usertimedout). Over IRC, the user would've received a NOTICE with a msg-id=msg_timedout and a message that includes the remaining duration in seconds. At the very least, the message in Helix should include the seconds. Ideally, the drop_reason contained an additional field with just the remaining timeout duration in seconds (if that's the reason) so clients can format (potentially localize) the message.

   • When attempting to send a non-existing command through the API (e.g. sending "/foo" or ".foo"), the message is dropped with a generic error: "Your message is being checked by mods and has not been sent." At the very least, that error should hint at the command. Ideally, that message is sent as-is.

   In general, we noticed, that "Your message is being checked by mods and has not been sent" is a frequent error. However, in many cases, it's wrong, and the message will not be seen by mods as it never went through.

   Documentation for the error codes would be great too (there's an open issue for it).

   When switching from IRC to the "Send Chat Message" Helix endpoint in a third party chat client, we noticed that the error messages were less descriptive when compared to some of the NOTICE messages received through IRC.

   • When a user is timed out and attempts to send a message, they get a drop_reason of "You are timed out from talking in the room." (code: usertimedout). Over IRC, the user would've received a NOTICE with a msg-id=msg_timedout and a message that includes the remaining duration in seconds. At the very least, the message in Helix should include the seconds.… more

   14 votes

   Vote 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

   Submit Rating

7. Get VIP Channels Endpoint

   Provide an endpoint where the authenticated user can retrieve all channels where they are granted the VIP role.

   Since Eventsub doesn't return userstate responses like IRC does, we aren't informed of vip status on channel.chat.message subscribe, message events, or helix send responses. We can manually check VIP status by referencing if we have the VIP badge after sending a message; however it would be nice to fetch all VIP channels from a helix endpoint, much like '/moderation/channels'.

   Use case for this would be chatbots which scale permissions based on VIP/mod status.

   46 votes

   Vote 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

   Submit Rating

8. Get Streams by platform/device

   When using the Get Streams endpoint (https://dev.twitch.tv/docs/api/reference/#get-streams). It would be great if you can add a query parameter to get live streams from specific device(s) only.

   Use Case:

   I run a PlayStation themed website and app (Pocket PSN) where users can link their Twitch accounts. I would like to create a live stream section that shows a bunch of live streams from our users, however, I would only want live streams from PS4/PS5 consoles.

   This is to prevent people from simply linking their Twitch and streaming games from a PC or games that don't even exist in the PlayStation library. This would also be a more accurate portrayal of the game (eg: beefed up PC specs may show a game in much higher quality than what the PlayStation is capable of...or visa versa)

   EDIT: Also making platform/device a part of stream.online event subscription. (https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#streamonline)

   When using the Get Streams endpoint (https://dev.twitch.tv/docs/api/reference/#get-streams). It would be great if you can add a query parameter to get live streams from specific device(s) only.

   Use Case:

   I run a PlayStation themed website and app (Pocket PSN) where users can link their Twitch accounts. I would like to create a live stream section that shows a bunch of live streams from our users, however, I would only want live streams from PS4/PS5 consoles.

   This is to prevent people from simply linking their Twitch and streaming games from a PC or games that don't even exist in the… more

   2 votes

   Vote 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

   Submit Rating

9. Add an API endpoint to track individual moderator activity

   I propose introducing a new API endpoint that allows streamers to track the activity of each individual moderator. This endpoint would provide detailed statistics on actions such as the number of bans, timeouts, and deleted messages performed by a moderator over a specified period.

   Currently, monitoring moderator activity is a time-consuming process. While it is possible to use custom bots to extract this data by scrolling through the existing moderation activity logs, the process is inefficient, as loading the logs becomes slower with larger datasets.

   This new endpoint would significantly improve efficiency, allowing streamers to quickly analyze their moderators’ contributions and take appropriate actions, such as removing inactive moderators. It would ensure that streamers are informed about the engagement levels of their moderation team without relying on slow and manual methods.

   I propose introducing a new API endpoint that allows streamers to track the activity of each individual moderator. This endpoint would provide detailed statistics on actions such as the number of bans, timeouts, and deleted messages performed by a moderator over a specified period.

   Currently, monitoring moderator activity is a time-consuming process. While it is possible to use custom bots to extract this data by scrolling through the existing moderation activity logs, the process is inefficient, as loading the logs becomes slower with larger datasets.

   This new endpoint would significantly improve efficiency, allowing streamers to quickly analyze their moderators’ contributions… more

   9 votes

   Vote 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

   Submit Rating

10. Who and when snoozed / ad schedule updated

    Please provide an eventsub topic(s) that

    • notify when a snooze is used
    • notify when the schedule is updated

    Knowing when a snooze is used can stop two moderators using the same tool from both snoozing and burning 2 snoozes at the same time when only one was needed.

    Or even all three snoozes if three mods snooze without checking that another mod snoozed.

    Additionally knowing when the schedule updates (next ads changes when it's due or it's duration) can assist and/or instant notification when a snooze refills

    17 votes

    Vote 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  ·  EventSub  ·  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

    Submit Rating

11. Allow creating guest star sessions on behalf of streamer without call interface

    Currently, guest star sessions while IRL Streaming are complicated because the streamers need to be logged into a PC in order to enter a call.
    Please add the possibility to either:
    1. join Guest Star sessions in the mobile app (and possibility to run it in background), or
    2. add a permission which has to be granted on authorization to start, join and run Guest Star sessions. To ensure streamers safety, you could send notifications in Twitch to confirm Guest Star sessions and additionally provide a button in the dashboard to stop a running Guest Star session immediately.

    Thank you and best regards,
    Lucas

    Currently, guest star sessions while IRL Streaming are complicated because the streamers need to be logged into a PC in order to enter a call.
    Please add the possibility to either:
    1. join Guest Star sessions in the mobile app (and possibility to run it in background), or
    2. add a permission which has to be granted on authorization to start, join and run Guest Star sessions. To ensure streamers safety, you could send notifications in Twitch to confirm Guest Star sessions and additionally provide a button in the dashboard to stop a running Guest Star session immediately.

    Thank you… more

    3 votes

    Vote 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

    Submit Rating

12. Add EventSub Subcriptions for 3rd party events

    With Twitch having its 1st party alert box system linked with 3rd party events (Crowd Control, StreamElements, Streamlabs & Throne). It would be nice for EventSub to have subscription to those events too.

    2 votes

    Vote 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  ·  EventSub  ·  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

    Submit Rating

13. Issue with Helix API’s game_id Field for Completed Streams

    When using the Helix Get Streams endpoint, I’ve noticed that once a stream ends, its metadata no longer includes the gameid (or gamename)—even if the broadcaster had correctly tagged a category while live. This makes it impossible to retrospectively determine which game was played in past sessions.

    Steps to Reproduce:

    Call GET https://api.twitch.tv/helix/streams?user_login=<streamer>

    While live: Response includes non-null gameid & gamename when the streamer has set a category.

    Immediately after the stream ends: Same call returns gameid: null (and omits gamename).

    2 votes

    Vote 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

    Submit Rating

14. Getting ban events shouldn't moderator scope with EventSub

    IRC's CLEARCHAT has ban-duration accessible at all scopes, but EventSub's channel.ban requires channel:moderate scope, i.e must be a mod. This information is normally available to all chatters; 3rd party chat programs cannot migrate from IRC and retain feature parity

    Either the information should be provided via channel.chat.clear_user_messages, or, better, the scope for channel.ban should be expanded. Information can be restricted if the scope does not have channel:moderate.

    4 votes

    Vote 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  ·  EventSub  ·  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

    Submit Rating

15. Subscription-Message Endpoint emotes update

    Currently the channel.subscription.message EventSub provides a message object in the payload that does not match the format of message objects in nearly any other EventSub (example, channel.chat.message or channel.bits.use). The version of the message object that provides the fragments would be ideal for use in the channel.subscription.message EventSub as well. I would encourage the development of this as a "version 2" of the channel.subscription.message EventSub, just like the version 2 of the channel.channel-points-automatic-reward-redemption.add EventSub

    I think this could even be added to a version 2 of the channel.cheer EventSub and any other EventSubs that have message objects.

    2 votes

    Vote 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  ·  EventSub  ·  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

    Submit Rating

16. Plus Points as an API

    Similar to https://twitch.uservoice.com/forums/310213-developers/suggestions/39817966-provide-api-to-return-subscriber-points please provide a way to obtain the Plus Points of a channel.

    We'd like to build/create out own on screen widgets to help a streamer get towards the various Plus Program goals

    Alternatively modify the Twitch provided widget to be a true creator goal instead of a seperate widget and third parties and consume that instead.

    32 votes

    Vote 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

    Submit Rating

17. Provide an EventSub subscription for people knocking

    I would like to be notified by EventSub when a broadcaster receives a knock from another broadcaster who wants to use Stream Together.

    7 votes

    Vote 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  ·  EventSub  ·  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

    Submit Rating

18. need dark mode for the Chat embed html part

    <iframe id="twitch-chat-embed"
    src="https://www.twitch.tv/embed/twitchdev/chat?parent=dev.twitch.tv"
    height="500"
    width="350">
    </iframe>

    2 votes

    Vote 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  ·  Embeds  ·  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

    Submit Rating

19. channel.moderate V2 doesn't tell Timeout duration

    To date, there's no way to accurately know how long a user has been timed out for.
    We only get a "expires_at" date that tells when the TO ends.
    We can kinda compute the duration by making the diff between this date and the "message_timestamp" from the event, but it is not accurate and can be off by 3s or more from a few tests.

    Having a "duration" field with the number of seconds the user has been TO for would be nice to avoid this issue.

    11 votes

    Vote 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  ·  EventSub  ·  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

    Submit Rating

20. Add "last predictor" in channel.prediction.progress

    Similar to "last_contribution" for "channel.hype_train.progress", there could be a field indicating the last predictor with informations similar to what's already in "top_contributors" for each outcome.
    If progress does indeed send a notification for each participating user, it wouldn't be much more cumbersome to add this field.
    Furthermore, this would allow:
    - reliable, real-time information for an interactive infographic.
    - a low-cost option to retrospectively count the number of points spent and earned by each user during this prediction.
    - a "best predictor" statistic with information on the user who won the most (in number of points or in pure victory).
    - statistics (I love statistics).

    Similar to "last_contribution" for "channel.hype_train.progress", there could be a field indicating the last predictor with informations similar to what's already in "top_contributors" for each outcome.
    If progress does indeed send a notification for each participating user, it wouldn't be much more cumbersome to add this field.
    Furthermore, this would allow:
    - reliable, real-time information for an interactive infographic.
    - a low-cost option to retrospectively count the number of points spent and earned by each user during this prediction.
    - a "best predictor" statistic with information on the user who won the most (in number of points or in pure victory).… more

    2 votes

    Vote 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  ·  EventSub  ·  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

    Submit Rating