105 results found
-
First Time Chatters Allow the
channel.chat.message
EventSub subscription to include if it is the first time the user has sent a message in the given channel.We can see this with IRC but not EventSub.
I understand only broadcasters or moderators can normally see that directly from native twitch chat without extensions, so possibly a scope or moderator status would be required.
It would just be nice to retain that information because it is useful for streamers who might use chatbots to respond to first time chatters with a welcome message. Also it is useful for moderation tools to see if a flood…
7 votes -
Inconsistent scope html formatting Scope formatting inconsistency. The channel.chat.usermessagehold and channel.chat.usermessageupdate sections have the word "scope" inside the code tag instead of outside like the other sections.
1 vote -
EventSub receive whispers EventSub recently got a few new chat-related subscription topics, most notably receiving chat messages, as described here: https://discuss.dev.twitch.com/t/available-today-twitch-chat-on-eventsub-an-api-for-sending-chat-and-the-conduit-transport-method-for-eventsub.
Our chat bot, and I imagine other peoples' bots might as well, is reacting to incoming whispers. To be able to migrate off of IRC it would be necessary to also add a new subscription topic for receiving whispers.1 vote -
Add EventSub topic for when viewers follow others through a shoutout you gave It would be nice to be able to have bots/alerts respond to when viewers follow a streamer shouted out on the channel they're being shouted out from.
Often when getting a raid and shouting out the raider I can't tell if anyone actually follows through with following the person who raided.
The ability to provide an alert, or chat message thanking those who click the follow button could improve the engagement on shout outs. Or at the very least provide insight to the streamer if they're being effective at promoting others.
1 vote -
Include moderator info in chat clear/message delete events The
channel.chat.clear
,channel.chat.clear_user_messages
, andchannel.chat.message_delete
EventSub events include the info of the broadcaster and (in the latter two) the info of the affected user. If we subscribe with a broadcaster or moderator token for that channel, we should also receive the info of the moderator that performed the action, similar to how we can see that info in the Twitch dashboard/mod view. This would also make them consistent with other events like ban/unban, shoutout create, etc.8 votes -
Shard selection in subscriptions created in a counduit I think it would be useful to add the possibility to select in which shard in a conduit a subscription will be created. This would made the developer to have more control over subscriptions created in a conduit. I think this feature would fit in as an optional parameter in the request body at creating a subscription within a conduit.
I know the conduits are made to balance the traffic over shards and connections but giving the developer more controll over which subscriptions goes in which shards is something that will make developing over conduits better.
In my opinion this…
1 vote -
Add cumulative subscribed months for `channel.chat.notification` sub_gift notices sub_gift
notifications viachannel.chat.notification
events don't contain a field for the cumulative number of months the gift recipient has subscribed to the channel. This is however exposed in IRC via themsg-param-months
tag in the equivalent subgift USERNOTICE.Please, consider adding this information to Eventsub too for consistency
8 votes -
EventSub channel.chat.message improvements As of now, the new
channel.chat.message
notification is a nice addition to the EventSub system.
But I'd love to get some more information about the user sending the chat message, slightly similar to the IRC implementation but still less verbose.In comparison to the IRC, I miss some flags like
isVip
,isSubscriber
,isModerator
, maybe evenisEmoteDesigner
(?). I'd be also great to have something likeisFollower
, same for the IRC implementation.When developing a 3rd party system to allow broadcasters to implement chat commands, this would really improve the usability of this event messages and could…
4 votes -
All time user bits in cheers payload. Previously PubSub had a field called "bitstotalused" in a cheers payload that represented all-time user bits which is not currently available in EventSub events. This is an important data that I was using to cache data for custom leaderboards widget that requires any data prior to its existence. Unfortunately, to obtain this data you have to make a Leaderboard API call by user_id, which is really inconvenient.
2 votes -
Add channel.ad_break.upcoming for upcoming ads Twitch Dashboard allows the broadcaster to configure a notification for an upcoming ad, up to 20 minutes in advance, and allow for a snooze.
If the broadcaster has enabled this feature, I'd like for Twitch to send a channel.ad_break.upcoming event over EventSub, so I can trigger actions off of that.
5 votes -
Enchance cheering eventsub(s) to include pin information With the changes coming to HypeChat and Cheering
A cheer can/will be pinned in the pin bar
Please enchance the relevant eventsub topics to include pinning information
We'll also need a new EventSub topic for "cheer was unpinned" for when that cheer was autounpinned due to timeout or unpinned due to user/moderator action
4 votes -
MQTT Transport Are there any plans to implement MQTT as an available transport? It seems like the protocol's architecture suits EventSub very well and might make EventSub easier for developers familiar with it.
Not sure how authorization would be handled. That might be a chore, but if it's worth the effort involved it would be cool to have.
2 votes -
EventSub topic for a Story being published Please provide an eventsub for a Story being created/published for a given channel.
11 votes -
Mention the limit on the JOIN/PART message page Why doesn't this page mention this only works on smaller Twitch streams? There is currently no indication that this wouldn't work for bigger size streamers, other than a few forum posts from years ago.
2 votes -
Guest Star events should allow guest_id as a condition as a streamer, I want to be able to subscribe to Guest Star events that involve my user id as a guest; currently, I can only subscribe to events using the host channel's ID as the condition.
1 vote -
Fix problem when verifying callback The line
res.status(200).send(notification.challenge);should be:
res.set('Content-Type', 'text/plain').status(200).send(notification.challenge);2 votes -
EventSub Hello World Without code samples/examples, I find the documentation minimally useful. I've got a clientid, clientsecret, appid, appsecret, token? Bearer token, eventsuburl, callbackurl, etc. While I appreciate you listing what RESPONSE might look like, it would be nice to see at least a basic "hello world" code sample. For example, since minimal auth (none?) is needed to subscribe for when a streamer goes live, it seems that would make a nice example of the overall flow.
1 vote -
mystery_only condition for channel.subscription.gift Adding to these ideas:
https://twitch.uservoice.com/forums/310213-developers/suggestions/44500245-revise-the-channel-subscription-topics
https://twitch.uservoice.com/forums/310213-developers/suggestions/43813413-provide-a-gift-event-id-in-the-channel-subscribeAdd a "mystery_only" boolean condition to channel.subscription.gift so that channel.subscription.gift only triggers when a mystery gift event happens.
2 votes -
Add EventSub events for channel point goals (start, contributions, end) While the API doesn't support channel point goals at all right now, I think it would be beneficial for developers to have ways to read the progress of channel point goals, for example for displaying the progress on overlays or having events triggered when it finishes.
1 vote -
Identify moderators who have created or completed predictions I am in the case of a big streamer who has dozens of moderators. We do not have the possibility to know, neither by EventSub, nor by API, which is the moderator who created or ended a prediction. It's annoying because it happens very regularly that some do anything.
Would it be possible to add moderatorid, moderatorlogin and moderator_username information on the prediction creation and resolution events?
4 votes
- Don't see your idea?