-
Allow channel moderators to control polls/predictions over the API The endpoints announced earlier today ( https://discuss.dev.twitch.tv/t/announcing-apis-and-eventsub-for-polls-and-predictions/31539 ) should be usable by channel moderators so that third-party apps like Chatty can make use of them without the broadcaster needing to authenticate.
153 votes -
Please provide an API for the new "Unban Request" system So that third party developers can be notified of new unban request
And that third party developers can respond to those unban requests, the same way as you can on the moderator view124 votes -
Delete clips There is no API methods for deleting a Clip
Please provide a method
103 votes -
Create Custom Reward: can't provide custom image Create/Update doesn't provide the ability to upload/change images for a reward.
This would be useful.
Alternatively if we can't do upload initially.
Add the ability to specify a channel emote (either by coDe or ID) so the reward would "copy" the channelEmote for that channel in.
So if I create a reward for CohhCarnage I can pick a cohhEmote (but I can't pick a liriki emote)
Or specify a URL to fetch a Image from
86 votes -
Expose id of the user who initiated the ban/timeout For /moderation/banned and /moderation/banned/events.
67 votes -
Allow getting realtime updates on polls/predictions/channel points redemptions through websockets for all users If would be very useful for chat clients or chat overlays to be able to show live updates on these features. Currently they are only available for the broadcaster (redemptions) or not at all through websockets (polls/predictions).
Ideally this would be available for all users to receive, just like chat is (which allows more simple integration into all kinds of tools), but even just mods using third-party moderation tools would already benefit greatly from this.
I included all three of those features, since they all seem to follow the same idea of only allowing the broadcaster access to that information…
34 votes -
Provide Cheermote and Emotes information for EventSub Cheer Events When viewers cheer, they use cheermotes and commonly emotes in their cheer messages. Unfortunately, the payload received from EventSub's
channel.cheercallbacks only have the raw text as entered by the user, with no indiciation of which portions of that text are cheermotes nor emotes. Thus, I propose the following update to the callback payload, similar to thechannel.subscription.messageevent, that passes along the data for both so that a consumer of EventSub can reconstruct the message:
…{ "subscription": { ... }, "event": { ... "message": { "text": "Rah Rah Cheer! cheerwhal1 Cheer100 notACheer101 finite6ThrowBall", "cheermotes": [ { "begin": 16, "end":16 votes -
Also provide in channel.cheer an array of bits used Summary:
A cheer message can be multiple cheers in a single payload. Providing the individual cheer components in an int array would provide data that is not currently there. Emote placement, while also desired, would be still more work than should be necessary at first glance to determine the bits used.Example: **
BarryCarlyon PogChamp100 PogChamp100 Party100 Wow Soaryn is Frustrated!
This would result in **"bits": 300; however this is incomplete and would be desired to also have something like "bits_used": [100,100,100]Reasoning:
While again, emote placement would help, determining the bits used from it would be extra and redundant…14 votes -
Copy Hype train Begin/Progress/End for outbound raids 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.
10 votes -
Provide Hype Train Begin level 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.end10 votes -
channel.update or stream.online - add live-notification message to payload To forward live notifications, it would be awesome to also receive the live notification message the streamer has set - either when they set it with channel.update and/or when the stream goes live.
7 votes -
Extend Automod Status Please extend
https://dev.twitch.tv/docs/api/reference#check-automod-status
To provide as much information as the new PubSub Topic for
automod-queue.<moderator_id>.<channel_id>doeshttps://dev.twitch.tv/docs/pubsub#topics
Currently the API jsut does pass/fail
But PubSub provides content/text/frames/reasoning.This endpoint may be used by third party tools such as tip alerts or extensions to determine if a message passes review or not.
And if it is to be held and presented in a dashboard for moderation staff to review would be useful to include the additional information/reasoning for the block.
5 votes -
Responsive Embed Widgets The "Embed everything", "Embed Video", and "Embed chat" widgets should be responsive instead of a fixed width and height. Or if we specify the width, at least automate the height so it respects the aspect ratio.
3 votes -
Add an `emote_type` "filter" as an optional parameter So a developer can ask the api for just bits reward tier emotes or the "regular" sub emotes
This applies to both
- Get Channel Emotes
- Get Emote Set
3 votes -
hype train With the way how certain bots work, Webhooks wouldn't work with said bots. So my Suggestion is to include PubSub so more bots can utilize features like Hype Train and other stuff included on twitch.
3 votes -
Embeds should have language parameter Our live events are in french. We would like the chat embed widget to be in french, or at least give us the option to change the text of what's visible like the "Send a message", "Chat", and "Welcome to the chat" messages.
2 votes -
ban event include data from helix banned events Include the same data as received from https://api.twitch.tv/helix/moderation/banned/events. Primarily event timestamp (time when the ban/unban action occurred) and the id (allows checking for duplication with eventsub messages already received when pulling from helix)
Add the following fields to "event" paylod for ban/unban eventsub messages:
"id": "1IPFqmlu9W2q4mXXjULyM8zX0rb",
"action_timestamp": "2019-03-13T15:55:19Z"1 voteThank you for the feedback. We will investigate and consider making these updates.
- Don't see your idea?