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.

Add three topics

• Raid Begin, a channel started a /raid
• Raid progress, the number of users in the raid changed (sensibly capped so not too spammy on the webhook, but if socket, more spammy perhaps)
• Raid End, raid completed or was cancelled.

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

Now that Twitch is utilizing IGDB instead of Giantbomb.

Please add the IGDB Game ID to the Helix Fetch Game endpoint.

https://dev.twitch.tv/docs/api/reference#get-games
https://api-docs.igdb.com/#game

Then we can easily lookup a game on Twitch with the game on IGDB without getting lost in search/selecting the wrong one with a similar name

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.

Extend

https://dev.twitch.tv/docs/api/reference#get-eventsub-subscriptions

To add a optional query string param of id to allow developers to lookup a single subscription.

If a developer stores the ID's when the subs are created, they may want to spot check a single ID's status, or check the settings of it, without having to paginate or manually filter the results returned when using on of the currently offered filter options

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

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.

Add parameter to enable dark mode for chat please.

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

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.