What's been made available for the events from PubSub is nice, but currently there is no way to know of when a unfulfilled reward has been marked as complete by a Streamer/Mod. Since the event is already well structured, all that would need to be done is simply re-send the same event with the status property updated to reflect that it was fulfilled (either just using the existing "FULFILLED" value or possibly a new value like "MANUALLY FULFILLED").

Add parameter to enable dark mode for chat please.

Add subscriptionStatus to extension JWT. Currently subscriptionStatus is in Twitch.ext.viewer. With it in the JWT, it can be verified by an extension backend.

Emotes are a commonly used feature of Channel Point Redemptions requiring messages. Unlike the EventSub Subscription Message events which provide emote ID and placement data, Channel Point Redemption events do not. I propose the following change to the Point Redemption notification payload:

channel.channel_points_custom_reward_redemption.add and channel.channel_points_custom_reward_redemption.update:

{
    "subscription": {
        ...
    },
    "event": {
        ...
        "user_input": {
            "text": "Channel Point Message! finite6ThrowBall",
            "emotes": [
                {
                    "begin": 24,
                    "end": 40,
                    "id": "emotesv2_4133039724974aa59589549eae677d03"
                }
            ]
        },
        ...
    }
}

This allows for a client to properly construct the channel point redemption input, with emote images, similar to the channel.subscription.message event.

This is more of a uncertainty of necessity, as the hype train documentation is still fairly new to me. As a broadcaster there have been scenarios where a level 5 hype train was the starting level.

Providing the level at the start could alleviate some confusion for progress and end as well as provide some consistency for the other two event types.

Reasoning:
The hype train on the end user side could start at a completed level 5. Depending on when the event is actually sent, this could provide odd results.

Related events:
- channel.hype_train.begin
- channel.hype_train.progress
- channel.hype_train.end

Make more developer tools for working with embedded clips.
At least, it can be the same tools as for the VODs player (playback api, events etc). Or you can add more features specifically for clips, for example, when you put an array of clips into player it displays as a collection or playlist.

Being able to order some of the Helix endpoints by date would be useful

Follower for example would need in some cases 11k+ calls to the follower endpoint to just get the 100 followers who had followed for the longest time.

This would also be good in the subscription endpoint if cumulative and streak get put into the Helix API

It would be convenient to have the ability to query Bits transactions based on broadcaster id and user id. This is extremely helpful for Extensions with lots of transactions and saves on calls to the API that would be necessary for paginating until the desired transaction is found.

Add viewer and channel count in /helix/games/top response. This information is currently not available in Helix.

Currently, this endpoint: https://tmi.twitch.tv/group/user/<CHANNEL>/chatters

Can be used freely without any authentication or scope.

This is definitely being abused with the hate raids. It's been abused by malicious actors for a long time now. Why has this endpoint been created in such a way that there is zero barrier for a malicious actor to obtain user data?

Even the Get Polls endpoint (https://dev.twitch.tv/docs/api/reference#get-polls) requires both authentication and a scope!

How has that Get Chatters endpoint not yet been removed an replaced with a secure Helix endpoint, as stated here: https://twitch.uservoice.com/forums/310213-developers/suggestions/39145294-chatters-viewers-helix-api-endpoint

This is not ok.

When a user connects to IRC, the USERSTATE command gives a emote-sets list, this does not contain unlocked bit emotes and I'm guessing it also doesn't include follower emotes and animated emotes. This should be fixed.

IRC has a number of "upgrade" events

giftpaidupgrade / anongiftpaidupgrade and one related to "prime to real" that I don't have the tag/msg-id for

A "subscriber upgrades" topic would be useful, if this doesn't fall under "sub notifications" - https://twitch.uservoice.com/forums/310213-developers/suggestions/42008104-please-provide-an-event-sub-that-emits-sub-notifi

I could see a benifit to having this as a seperate topic, or tied into the "notifications" topic

An idea I had a while ago but never copied it to uservoice

Please provide

https://www.twitch.tv/products/STREAMER / the information in the "Subscribe popup"

as a end point

To return the

• product names
• emotes per tier
• is ad free enabled
• sub badges
• any emote modifiers

Optionally include the users progress to the next sub badge if authenticated as a user

It would be nice if you could filter the response of the subscription status endpoint with a transport filter (e.g. "?transport=websocket").

Its not a big deal at the moment because there only is one transport (webhooks) available but with more transports added down the line this would be a huge QoL improvement.

Could you please add documentation about how the chat filters feature in web chat is implemented? Other chat client could really benefit from filtering those messages or highlighting them for moderators as suspicious behavior.

To pin point the exact feature I provided screenshots from the official web browser chat:
- in action: https://i.imgur.com/CfzMx0z.png
- and the associated settings: https://i.imgur.com/8dYADBk.png

Currently twitch embed does not support vod chat and neither does the helix api.

Twitch only allows vod chat to be seen directly on the website.

This data could be used in a great number of ways by third-parties particularly video editors.

Please add a way to retrieve chat for vods

No? ok. Sadge

https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#userauthorizationgrant

Please extend user auth grant to include

• all scopes shared between ClientID and userID
• new scopes added to the relationshio when the auth occured

Possible use cases include: auto determine from this eventsub, what other eventsub topics to auto create.