39 results found
-
Please provide an eventsub topic for HypeChat Please provide an eventsub topic for HypeChat so third parties can build Custom Overlay integrations and tie the information into other systems a channel may have including but not limited to custom analyitics or credit rolls and so on
49 votesClosing due to the deprecation of Hype Chat. The related feature requests for pinned Cheers are https://twitch.uservoice.com/forums/310213-developers/suggestions/45606931-please-provide-an-eventsub-for-pinned-messages-add, https://twitch.uservoice.com/forums/310213-developers/suggestions/47450213-enchance-cheering-eventsub-s-to-include-pin-infor
-
HypeChat History API If our eventsub consumer is down we'll need to catch up
Provide an API to return recent hype chats (similar to hype trains that only keeps the last 7 days or so of data)
40 votesClosing the suggestion given the deprecation of Hype Chat in favor of pinned Cheers.
-
HypeChat Settings API Please provide and API to get/set the relevant HypeChat settings (broadcaster scoped)
In case a given channel needs to defer control of the settings to a authorised user, for things such as as hate raid defence on a given day we attempt to disable hype chats for the content being streamed.
35 votesClosing the suggestion given the deprecation of Hype Chat in favor of pinned Cheers.
-
HypeTrain - HypeChat Since HypeChats count towards HypeTrains.
Both the EventSub and API offerings for HypeTrains need to be revised to include this new information
10 votesClosing the suggestion given the deprecation of Hype Chat in favor of pinned Cheers.
-
Shoutout Create EventSub Subscription should not require moderator auth channel.shoutout.create currently requires a moderator/broadcaster token.
This defeats the point of a shoutout; channels do shoutouts exactly because they want other people to notice them. Restricting this subscription type prevents third-party chat applications from informing non-mods that a shoutout has taken place (thus defeating the point of the shoutout)
Please remove the moderator scope requirement on channel.shoutout.create
6 votes -
Add tier for subscriptions for the Hyptrain contributions Currently, you can't tell if someone has gifted tier 1, 2, or 3 subscriptions. It could be a tier 3 subscription or 3 tier 1 subscriptions. Therefore, the information should be added.
2 votesSubscribe to the channel.subscription.gift subscription type for gift subscription notifications.
-
Add Hosts to EventSub Currently EventSub allows subscriptions for Subscriptions, Gifted Subscriptions, Raids, Follows, and Cheers - All things that streamers like getting alerts for and calling out. However, it appears to be missing the ability to subscribe to being Hosted, another even that streamers thank their viewers for.
I know that in theory, Hosts are handled by Notice messages, but as they are only sent to the broadcaster, chat bots are unable to act on the alerts. Obviously the data is available somewhere, since all the major bot services can trigger alerts, but for those of us that are trying to make our…
43 votes -
Extend the maximum length of a prediction https://dev.twitch.tv/docs/api/reference#create-prediction - the maximum prediction_window is 1800 seconds (30 minutes). This seems unnecessarily short, there are some predictions I run that could be open for longer.
Imagine a prediction that lasts across the full length of a game, or even an entire stream--these generally run for hours, not just 30 minutes.
Please raise the maximum prediction_window significantly, to at least 2 hours, or longer.
4 votesThe Twitch API cannot create a Channel Points Prediction with a length longer than what is available in the Creator Dashboard. At this time, Predictions can be set in the dashboard to a number of options from 30 seconds to 30 minutes. Since implementation is not possible, I will close this post, however, I would recommend creating a suggestion in the Predictions category for a longer length. If implemented, that would also result in the API updates for third-party developers.
https://twitch.uservoice.com/forums/932221-channel-points?category_id=396184
-
Moment Endpoint Currently Moments are still in beta, but there is a /moment chat command so this UserVoice is for that to be implemented as an endpoint when it's out of beta.
Since moments are essentially clips with some extra bells and whistles, it could be almost a copy/paste of the Create Clip endpoint, and having the option of using 3rd party tooling could result in increased usage of the Moments product.
2 votesDeclining due to the Moments shutdown in October 2023.
-
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 votesWith the removal of the broader hosts feature last year, we are closing out this suggestion for host notifications via the API.
-
Hosts in Helix Please provide a Helix endpoint for inbound and outbound host status/information
and by extension a webhook
59 votes -
Add channels.host Webhook Type Trigger: Triggers whenever a broadcaster hosts on a broadcaster's channel.
Motivation: To my knowledge it is not possible to query hosts in real time. In our Twitch Alerts Extension it is currently not possible to show when a streamer is hosted by another streamer.
57 votes -
Cancel the new OAuth for Helix requirements As well discussed and pointed out in the announcement thread (ref 1). It makes no sense, The matching client id can be grabbed from the oauth url as ClientID's are public right? Atl east your own documentation says so (ref 2) And if not grabbed from the url they are publicly displayed with matching user data and scopes when sending a request to https://id.twitch.tv/oauth2/validate which can be accessed with just a OAuth token. This change is gonna reach nothing but us having to make our code more complicated by having to consistently keep track of client id's that where used…
83 votesWe appreciate all the feedback on this requirement, and understand that it can present additional development effort. While we must continue to adhere to this requirement, we will be providing samples and some simple tooling soon to help reduce the effort.
-
Allow reading/editing of user's points totals for a channel If a streamer authenticates with scope
channel:manage:redemptionsor a new scope likechannel:manage:points, allow for the ability to- read a user's current points
- add points to a user
- remove points from a user
- set a user's points to a specific value
for that channel.
1 vote -
Get by Emoteset with invalid emote set ID 200's https://api.twitch.tv/helix/chat/emotes/set?emote_set_id=4545454545
Shouldn't this 404?
1 voteReturning a 200 with empty data should be the consistent behavior expected if no matching emote set is found.
-
Allow viewers to authorize a channelpoints transaction via API As it stands now, it is not possible to subtract channel points from viewers as there is no endpoint for it. After looking around online it seems to be because there could be malicious uses for the endpoint, where an application could drain/burn channel points from viewers.
To circumvent this, give us a way to ask the viewer to accept a "transaction". This could be a small popup above the chat with the:
Application name,
Amount of points,
A small description of the transaction.The application would get a result back whether or not the viewer authorized the transaction.
If…
1 vote -
Standardize user_id condition While creating a wrapper, I found the varying conditions for "user_id" to be frustrating and have resorted to creating a Map for subscription.type -> *_user_id condition. (broadcaster_user_id, from_user_id)
I think it would be easier to always have the condition be "user_id" for a user, and then allow a second property for modifying the scope of the condition. So in the instance of "users.follow", it might look like:
condition: { user_id: "1337" follow_source: "from" }What are your thoughts on this?
3 votes -
Channel point transaction in extension Like Bits transaction, it would be great to allow Channel points to be accessible from an extension.
The idea is to not expose channel points to the extension and work the same way Bits transactions are.
This would also need the addition of channelPointSku or allow sku product to have a bits value and/or a channel Point value.
- User click on a button
- Extension fires window.Twitch.ext.points.usePoints(pointsSku)
- User validate transaction
- (if user complete transaction )OnTransactionCompleted callback is fired with receipt containing channelPoint as the currency used
- (if user cancel or don't have the channel Points) onTransactionCanceled is called
To complete it,…
54 votesAt this time, we are purposefully only allowing Channel Points redemptions in the chat UI on Twitch.tv for a consistent viewer experience. Closing this suggestion for now to confirm this is not actively being investigated for Extensions.
-
Add link to ToS on landing page This page should include a link to the API ToS
1 voteThe Twitch Developer Services Agreement is located on the documentation landing page (https://dev.twitch.tv/docs) since it encompasses all of the Twitch developer products and services. However, you make a good point that perhaps this should be available on additional pages especially if you do not enter the site from the landing page, perhaps in the footer, which we will consider.
-
lol !/usr/bin/env/python
import BaseHTTPServer, SimpleHTTPServer
import sslcertfile = "./localhost.pem"
keyfile = "./localhost-key.pem"class RequestHandler(SimpleHTTPServer.SimpleHTTPRequestHandler):
def endheaders(self):
self.sendheader("Cache-Control", "no-cache, no-store, must-revalidate")
self.sendheader("Pragma", "no-cache")
self.sendheader("Expires", "0")
SimpleHTTPServer.SimpleHTTPRequestHandler.end_headers(self)httpd = BaseHTTPServer.HTTPServer(
('', 8080),
RequestHandler
)httpd.socket = ssl.wrapsocket(
httpd.socket,
serverside=True,
keyfile=keyfile,
certfile=certfile
)httpd.serve_forever()
2 votes
- Don't see your idea?