106 results found
-
Adding creator on EventSub poll and prediction begin Everything is in the title. Today we do not know who created the prediction or the vote. It is necessary to make an API call, which is really sad ...
1 vote -
Please provide a topic for extensions active on a channel Please provide a topic that emits when an extension is activated/deacted/changed in a slot on a channel.
I would not expect it to require a scope as https://dev.twitch.tv/docs/api/reference#get-user-active-extensions doesn't require a scope.
It would be useful to monitor/confirm into third party tooling that extensions have been updated, especially when the dashboard is used to update, or it's auto updated due to an extension/game automatic switch.
4 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.
6 votes -
Add "stream type" (subscriber only/eveyone) to channel.update Include the "type of stream" in channel.update
Either
- everyone
- subscriber only
8 votes -
Receive Extension Transactions for All Extensions on your own account Extensions themselves can sign up for webhooks for transactions, but those bit exchanges are completely invisible to the broadcaster. They can't make alerts, or estimate revenue, etc. I would love an event for any transaction make on any extension for the authorized broadcaster.
2 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_enabled
to return all subscriptions that died for any reason.5 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.
9 votes -
Extend Channel Points Custom Reward Redemption update to include whom did the update Updated
To declare which moderator/broadcaster/user did the update, and if it was API omit.
This may be more appropritate to add to the proposed moderator actions topic instead https://twitch.uservoice.com/forums/310213-developers/suggestions/42991875-please-provide-a-topic-s-for-all-kinds-of-moderat
This is useful to track which moderator handle the Reward Redeem (whatever it was). And/or track bad actors/mistakes.
3 votes -
status casing for EventSub channel.prediction.end EventSub Beta for channel.prediction.end event/status should be consistent with helix casing of status, i.e "Valid values are RESOLVED, and CANCELED."
1 vote -
status casing for EventSub channel.poll.end and channel.poll.progress EventSub Beta for channel.poll.end and channel.poll.progress event/status should be consistent with helix casing of status, i.e "Valid values are COMPLETED, ARCHIVED, and TERMINATED"
1 vote -
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 -
Limitations of property transport.secret (max length) Limits like max length for transport.secret property would be good.
1 vote -
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 -
streams.online for user This is something with the intention for client rather than server side.
So the idea is to subscribe to the streams.online topic but instead of specifying a broadcasterid you specify a userid. This topic would give the streams.online notifications for the broadcasters that the user is following and has notifications enabled for. You could subscribe to streams.online for each broadcaster a user is following which is indeed a possibility but at the same time cause a problem as some people follow a good 200-300 channels of which for quite a lot they probably don't even have notifications which…
2 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 -
Add Sub Goal Amount towards next Emote Slot to EventSub It would be great for alerts, and goal bars to receive the sub count information along with each event, similar to the progress on hype train, they push the total, goal, and progress in each event, so the precedent is there for eventsub to expend on the core data. Something similar to the dashboard data would be great
{
"count":1,
"score":1,
"countbreakdown":[{"plan":"1000","count":1},{"plan":"2000","count":0},{"plan":"3000","count":0}],
"scorebreakdown":[{"plan":"1000","score":1},{"plan":"2000","score":0},{"plan":"3000","score":0}],
"nextlevel":{"minimumscore":15,"emoticon_limit":2}
}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.
-
Filter status endpoint by callback URL Allow filtering the event sub subscriptions list by specific transport destinations
Some people may use a clientID to feed more than one application.
So being able to ask the API to filter by destination would be useful.4 votes -
Add Extension Broadcaster Ratings to EventSub topics Add an extension's broadcaster ratings to EventSub so we can get real time feedback on our extensions from broadcasters. This should be limited to app access token from the extension itself to subscribe.
5 votes -
Notification - Channel Points Custom Reward Update/Remove On "event" the field "broadcasteruserlogin" returns empty string. Works on Add.
Useful links:
https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types#channel-points-custom-reward-update-notification-payload
https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types#channel-points-custom-reward-remove-notification-payload1 vote
- Don't see your idea?