19 results found
-
Provide an eventsub for when a Shoutout occurs Please provide a topic for shoutouts occuring on a channel.
This allows bots and/or overlays to provide additional/supplementry messaging
43 votesWe released two new subscription types in open beta this week for when a channel gives or receives a shoutout.
-
Please provide EventSub for Charity donations Please provide an EventSub topic for Donations
Primarily for creating our own overlays and/or piping it into our exsiting systems that already are tied into existing donation/charity systems
30 votesThe Charity Donate subscription type is in open beta now. We may add more Charity subscription types in the future.
-
Please provide an event sub that emits "sub notifications" Please provide an eventsub notification topic for sub notifications
Which would be a "clone" of messages appearing in chat for sub/resub notifications
For resubs the chat message and emote placement would be included
41 votesMessages for new subscriptions and resubscriptions are available via the “Channel Subscribe” and “Channel Subscription Message” EventSub subscription types. https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channel-subscriptions
-
Please provide an eventsub that emits unsubscribe/subscription end events Using event sub it should be possible to ONLY use event sub to maintain a list of people subscribed to a channel. (after an initial paint from Helix)
Using the current topics it's not possible to do that.
I currently have to fetch once using helix, then use eventsub to get new subs.
Then fetch again later using helix to account for unsubs.26 votes“Channel Subscription End” has been added to EventSub. https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelsubscriptionend
-
Add Broadcaster ID query option to GET https://api.twitch.tv/helix/eventsub/subscriptions Add Broadcaster ID query option to GET https://api.twitch.tv/helix/eventsub/subscriptions so you can query on just broadcaster ID, so I can make sure all their subs are setup, instead of having to paginate through all my subs to check just a handful
23 votesGet EventSub Subscriptions now takes an optional user_id parameter.
-
Add a Hypetrain ID Premise: Currently there is no way to identify a hype train from start to finish fully. Adding an id (Guid) would help alleviate tracking the train as it progresses as well as after it has finished.
Expected:
hypetrain_id
be added to the begin, progress, and end payloads. Given a particular hypetrain, these events would have the same Id per hype train.Usecase: Being able to cache and query a hypetrain via id to infer if the train is still continuing. Using time, winds up as an oddity due to the elongation of time behavior when the goal is reached. This…
6 votesThe Hype Train Begin, Progress, and End payloads include an id field.
-
Predictions in eventsub Please add Prediction start/progress/end events to eventsub
14 votes -
Bans: who did the action Hydrate the bans topic to include the user_id, login of the user that performed the ban action
So add
moderator_user_id
moderator_user_login
moderator_user_name
to the event
9 votes -
Add channels.raid Webhook Type Trigger: Triggers whenever a broadcaster hosts on a broadcaster's channel.
Motivation: We get this information from the IRC. Such an event in the EventSub would save us an continuous IRC connection in the chat. Therefore we only need to rely on webhooks.
16 votesChannel Raid is now available. See the EventSub subscriptions page for more information: https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types
-
Add Display names to live reactionary chat data Any topic, that deals with reactionary events from chat such as cheers or subscriptions (new/resub/etc.) it would be beneficial to have a display name for all parties involved, the user who subbed, cheered, but also gifted, and broadcaster.
Reasoning:
- Various names have a certain capitalization that identifies that user. Without that there are cases that make the name very difficult to decipher for the viewer if the name appears on screen, due to all the letters being lower case or upper case.
- If the name was already displayed in chat, then this data should also propagate to the…10 votes -
Bans topic sends for timeouts and bans but doesn't differentiate The bans topic will send an event for someone getting banned or timed'out from the channel.
The bans topic doesn't tell you if it was a ban or a timeout.
- Timeout's either need to be a seperate topic (not preferred)
- The payload extended to include a time parameter, so timeouts can be differetiance (preferred)
(Webhooks have the same problem ironically)
6 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.end11 votes -
Typo in extension.bits_transaction.create text The section title under the payload section of the
extension.bits_transaction.create
event is "Channel Hype Train End Notification Example" when it should read "Extension Bits Transaction Notification Example"1 vote -
Add mod/unmod events and adding/removing editors Mostly for broadcaster tools which have some kind of permission system that allows mods (and now editors) specific access to features. This would remove the need for checking if the user is still a mod/editor.
4 votes -
Add a type filter to the status endpoint It would be nice if you could filter the response of the subscription status endpoint with a type filter.
E.g. you want to only list subscriptions of the type "channels.update" so you would add an optional query param of "?type=channels.update" or something like that.
This greatly improves the capability to only check the status of a subscription type you care of at that time instead of having to paginate through 20,30.40 or more pages of subscriptions.
8 votes -
Provide Who and Reason in channel.ban Summary:
In chat for the broadcaster and mods, when someone is banned the reason and responsible user is provided. Adding the user's identifiers and the message that was used when banning. Assuming there is a timeout equivalent planned or made this likely would need to be added there for consistency as well.Reasoning:
This allows for up to date reasonings for why someone was banned without having to request this info separately.Related Topics:
- channel.ban
- channel.unban6 votes -
Improve Doc "Create a subscription" for EventSub In https://dev.twitch.tv/docs/eventsub step "5. Return the value of challenge from the callback verification request to complete the verification process. Your response must be a raw string. If your server is using a web framework, be careful that your web framework isn’t modifying the response in an incompatible way. For example, some web frameworks default to converting responses into JSON objects.
pogchamp-kappa-360noscope-vohiyo"It is not understandable where need to send challenge variable, on what api endpoint? Please maybe add a curl example
1 voteWe’ve updated the documentation, so this issue may be resolved.
-
Ability to increase subscriptions limits We run a Discord bot on ~9M Discord servers. It announces streams in Discord servers.
We are subscribed to 1M+ twitch channels using webhooks and managed to get there by taking advantage of the rate-limit bump form you guys provided back then. But it seems like you guys stopped doing that.
Since we hit the limit of subs, we had to change the way we do it and loop over live streams using the API - which is suboptimal since we miss some streams and the announcements are delayed.4 votesWe recently updated our subscription limit logic in EventSub so that limits scale as your application grows. See https://dev.twitch.tv/docs/eventsub#subscription-limits for more information.
-
add started_at to stream.online Its basically just for caching the date for things like uptime saves resources on our end (not having to make the call to Helix/streams) and the 36 extra bytes don't feel like the end of the world.
1 vote
- Don't see your idea?