-
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 -
Subscriber upgrades IRC has a number of "upgrade" events
giftpaidupgrade / anongiftpaidupgrade and one related to "prime to real" that I don't have the tag/msg-id for
A "subscriber upgrades" topic would be useful, if this doesn't fall under "sub notifications" - https://twitch.uservoice.com/forums/310213-developers/suggestions/42008104-please-provide-an-event-sub-that-emits-sub-notifi
I could see a benifit to having this as a seperate topic, or tied into the "notifications" topic
9 votes -
Raids [beta] sends all raids even raids that don't appear in chat The raids beta topic, sends raids that don't appear in chat via the IRC raid USERNOTICE
Please either
- extend the payload to mark if a raid appears in chat or not
or
- provide a condition to ignore/include/only be "non chat raids"
or
- all of the above
Please do not remove non chat raids, as developers/streamers would like flexibility on what to actually notify for/collect data on.
Regardless of any limitations Twitch puts in place on what appears in chat.
Would also like to collect it for statistical purposes/reporting on small/large raids for a given stream.
There may also be an…
8 votes -
Add a transport filter to the status endpoint It would be nice if you could filter the response of the subscription status endpoint with a transport filter (e.g. "?transport=websocket").
Its not a big deal at the moment because there only is one transport (webhooks) available but with more transports added down the line this would be a huge QoL improvement.
8 votes -
Extend user.authorization.grant to include scope information https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#userauthorizationgrant
Please extend user auth grant to include
- all scopes shared between ClientID and userID
- new scopes added to the relationshio when the auth occured
Possible use cases include: auto determine from this eventsub, what other eventsub topics to auto create.
7 votes -
viewer count from eventsub Either as a topic fired on update or added to "channel.update".
Advantages to its own event will reduce polling during a live stream and allow twitch to schedule when it sends out events as it needs to keep things in balance instead of having to contact 3rd party developers.
7 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 -
Add a channels.adverts topic for advert running Twitch requires streamers to run more ads
We are building tools to help facilitate this
There is noting in the API to let us know when ads run
Please provide a topic for adverts running
7 votes -
Cheer emote placement Please update eventsub to provide emotes used and placement of the emotes in the message similar to chat message does in order to allow us to easily reconstruct a cheer message to look like it did in chat
similar to
Example
The "emotes" tag from https://dev.twitch.tv/docs/irc/tags#privmsg-twitch-tags
7 votes -
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_idbe 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 votes -
Add a topic for Roomstate changes including whom triggered it Chat has a number of states, slow mode/follower only mode.
Some moderationg applications involved monitoring for these states and responding as needed, and these applications will currently use PubSub but only in a logging capacity so alternatively connecting to chat for this data is perhaps overkill.
Please provide an eventsub topic that relays
- when/what Roomstate changes (slow on/slow off sub on sub off emote only)
- which moderator/user triggered the change.6 votes -
Provide a Redirect Event Summary:
Filling in the holes of what chat provides and EventSub provides would be appreciated. In this case hosts, raids, and potentially front page promo attributions. There isn't much reason to have multiple unique events in this case as all of the aforementioned events are the same, a provider of a redirect (user), a recipient (broadcaster), and an attribution amount (viewers attributed to the event). The only specifier needed is a type or context. However, different events wouldn't be necessarily rejected in concept, it would just seem unnecessary. Since a condition is sent for the subscription to the event, one…6 votes -
Various EventSub Thoughts The channel.subscription events are very lackluster. Aside from checking if it’s a gift, and what tier it was there isn’t much useful data here. Any chance we could see something like months total, moths streak, or the tier? I know this data is there in the subscriptions API call, just curious as to why it hasn’t been included in this release of the EventSub system. Seems like a miss there
The channel.ban/channel.unban events could/should be merged. Just smash em into one topic and include a tag: “isBanned” as a boolean. Seems silly to have them separate, in my opinion.
Loving…
6 votes -
Extend stream.offline to include the "true" end time of the stream (rather than using the timestamp in the header) stream.online has
started_atplease addended_atto stream.offlineSo stream duration can be determined as accurately as possible as needed./
5 votes -
Provide Title and Game information with stream.online Other than knowing someone is online, there is still a need to utilize the API for getting related information about a stream.
It would be nice to have an all-in-one "here's everything about this stream going live" instead of requiring additional calls (especially if there's a possibility of caching delays).
Something along the lines of the data provided for channel.update would be nice
5 votes -
Add whom did it to the Moderator add/remove topic If is possible for a user to demod themselfs.
And it's possible that a user can be modded by someone whom is not the broadcaster (in super rare cases)Please add this information to the Mod add/remove topic.
It's handy for tracking a "oh why is this person not a mod suddenly" as the broadcaster.5 votes -
Add current subscriber count and current sub points to payloads In subscription based events, add fields with the current number of subscribers and how many sub points the broadcaster currently has.
Since there is still no way to get these numbers except of iterating over the full subscriber list (which costs lots of requests on bigger channels) this would be an awesome addition to subscribe/unsubscribe/sub expired-events.Alternative: Subscriber count/Sub points change events. But that probably would be too many events on busy channels.
5 votes -
Add an Get EventSub Subscriptions filter of "not_enabled" So instead of doing 5 looksups for each kind of not "enabled" filter.
Add a filter option of
not_enabledto return all subscriptions that died for any reason.5 votes -
Add "stream type" (subscriber only/eveyone) to channel.update Include the "type of stream" in channel.update
Either
- everyone
- subscriber only
5 votes -
Return host notifications for hosts of ALL sizes Recently twitch removed notifications for smaller hosts. This is not ok. We want this back. We as a community need to band together to get this change reverted.
4 votes
- Don't see your idea?