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.

https://discuss.dev.twitch.tv/t/new-extension-policy-updates-including-a-moderation-section/24410/3

As noted for the new policy, we should prevent people banned/timed out from the channel, from submitting content.

Theres no way to do that without an extensions developer creating an external oAuth loop to request the relevant scopes from a broadcaster.

Duplicate the subscription scope capability to a the channel moderation scope to facilitate this policy being enforceable and negate the need for two sets of keys for each extension.

It is impossible to get the emotes for a channel from the API via Channel ID

The API uses "emotesetID" and there is no API endpoint that provides the emotesetID for a given channel

Please provide a way to get the emotes for a channel via ChannelID/ChannelLogin

Moderators are able to add a reason/description whenever they ban people in chat (/ban [username] reason)

This information is currently only available in the "not allowed to use" GraphQL-api, but should also be added to the documentet endpoints; /moderation/banned and /moderation/banned/events

(Ban-reason is different from moderator-comments.)

https://dashboard.twitch.tv/u/USERNAME/settings/moderation/blocked-terms

There is no API for automation of adding/removing/listing a given channels blocked-terms

When adding/removing a term modlogs display in chat as

> barrycarlyon used: /addblockedterm THISISATEST.
> barrycarlyon used: /deleteblockedterm THISISATEST.

But these are not valid chat commands either.

Please provide an API to CRUD channel blocked terms

In the channel settings, you may specify a "profile accent color" to represent your brand.
Right now, this isn't exposed in the API at all.

Similar to the Bits Leaderboard, please add a gifted subs leaderboard API, so we can see everyone who has gifted a sub in the channel.

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.

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.

When a VOD gets deleted, there's no known way to retrieve the time of when the clipped event occurred live. Knowing the time of the event helps tremendously when creating highlights for an individual as it allows chronological ordering with no errors, whereas if one uses the createdat_ key from the Get Clip api endpoint, you're subject to the time when the clip was created.

This topic was discussed briefly on the twitch developers forum, https://discuss.dev.twitch.tv/t/clip-event-timestamp/19441/3 .

When a caster leaves a review.

Currently we can only get these reviews manually via the console.

Please provide, one or more of:

• An API, to collect the spreadsheets like existing ext analytics


• An API, to collect the reviews,


• A webhook to collect reviews into our own system(s) in real time

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

Bit emotes which are earned from using emotes in a channel

Are not exposed in the API.

Please expose them

On the new Helix endpoint, https://dev.twitch.tv/docs/api/reference/#get-extension-transactions and therefor https://dev.twitch.tv/docs/api/webhooks-reference/#topic-extension-transaction-created the signed receipt that comes with onTransactionComplete from the JS Helper is missing. In order to audit and avoid man in the middle attacks, a signed JWT that can only be verified with the client secret should be sent on all endpoints sending monetary transaction data.

r9k mode
follower mode
subscriber mode
emote mode
slow mode

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