11 results found
-
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.
-
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.
-
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 -
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 -
Hosts in Helix Please provide a Helix endpoint for inbound and outbound host status/information
and by extension a webhook
59 votes -
Anonymized historical VOD chat I would like to use the comments on a VOD to detect moments of interests.
However the only way currently is through an undocumented and unsupported V5 API route that requires making several hundreds if not thousands of requests to compile the entire chat history of one video.
I understand that there are legitimate concerns about user privacy. However I think that the chat could be anonymized, stripped of each username. Even with this left out, making this available on the new Twitch API would be immensely helpful for services such as mine.
1 vote -
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.
-
Please add a "isAutohost" boolean to https://tmi.twitch.tv/hosts Currently we have to grab this Informtion about autohosts from the IRC Chat. But why? Why not just adding a boolean (for example: "isAutohost": true/false) into the already existing hosts endpoint for tmi.twitch.tv o.O?
Would love to have something like that. Thanks!
22 votesSee comment for more information.
- Don't see your idea?