From: https://github.com/twitchdev/issues/issues/63

Brief description
The channel:read:redemptions scope is required by the Channel Points PubSub topic (https://dev.twitch.tv/docs/pubsub#topics) but not mentioned in the scopes overview (https://dev.twitch.tv/docs/authentication#scopes)

Expected documentation
The channel:read:redemptions listed on the overview page (https://dev.twitch.tv/docs/authentication#scopes)

Now it is not possible to get the number of streams in a certain section without sending a large number of requests to the API.

Adding the commonly-used game title field to the Get Streams endpoint payload (similar to the addition of user name) will allow developers to make less calls for the data needed. In other words, Get Games would not need to be called for every game id to get one more field.

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

Add a Webhook for Cheers

The procedures are no longer clickable at https://dev.twitch.tv/docs/authentication#getting-tokens.

(for a clickable reference see https://web.archive.org/web/20191220122144/https://dev.twitch.tv/docs/authentication)

Add the gamename to the get streams endpoint in addition to the gameid this saves us an extra unnecessary call compared to kraken

r9k mode
follower mode
subscriber mode
emote mode
slow mode

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

Some third-party developers request id access on their Extensions just for the purpose of getting a viewer's username to build a more personalized experience. The only way to do so is by relying on the Helix user endpoint on their EBS. The Helix team already modified any payload that has a user id to also deliver a username and save developers the extra step of using the /users endpoint, so it's natural for Extensions to follow that path.

The current Helix endpoint doesn't give the broadcast ID, so there's no way to grab which broadcast the VoD is from.

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

The newly required parent field broke our mobile embeds! A workaround would be awesome, and a React Native SDK would be divine. Thanks!

Even tho https://twitch.uservoice.com/forums/310213-developers/suggestions/40340764-add-client-id-headers-to-examples is marked as completed the docs are still 90% outta date for helix changes (According to Barry)

https://dev.twitch.tv/docs/api/guide#rate-limits still talks about not provided tokens

https://dev.twitch.tv/docs/api#step-2-sample-code still doesn't use a OAuth token

https://dev.twitch.tv/docs/api#step-3-results Is incorrect because step 2 doesn't use a OAuth token

Add dark mode for chat embed theme: "dark"