-
Clips EventSub subscription type (retitled) Please provide a Webhook topic for when a Clip is created, edited or deleted
Also provide a notification for when a Clip reaches certain view milestones.
260 votes -
Extend Clips API to provide the MP4 url so editors can automate downloads If I have an oAuth that represents a User, where the User is either
- the broadcaster the clip is of
- an editor of the channel that the clip is of
- the user is the owner of the clip
And I make a request for a Clip as documented: https://dev.twitch.tv/docs/api/reference#get-clips
(but with the bearer naturally)
The JSON Response should include the direct link to the MP4 or an ability to download the Clip.
This is off the back of the removal/deprecation of some undocumented API's that I was using to get the MP4 URL for automated download for creation of clip…
223 votes -
Chatters / Viewers Helix API Endpoint The existing API endpoint for getting chatters predates User IDs and only returns usernames. It's also part of TMI and not officially documented, which could result in it being removed at any point without any notice.
Many bots use the endpoint for channel loyalty points, and then have to make secondary calls to the get the user ID.
198 votesWe are actively reviewing the use cases that were shared in the quarterly survey that closed on August 1. 72 developers provided feedback for this question, which we greatly appreciate! This will help us understand the best design for such an endpoint. Given this research, we will move the suggestion into "Investigating."
-
Improve the accuracy and precision of "hlsLatencyBroadcaster" in the Extension helper library. An improved "hlsLatencyBroadcaster" value unlocks and improves interactive experiences that rely on precise synchronization. For example, the Tobii eye tracker Extension and many Genvid Extensions that rely on this latency for accurate click or display location.
184 votesThis functionality may be considered in the future, and we appreciate the feedback and comments provided on this suggestion. There are some technical challenges to solve to provide a better experience for synchronous use cases, though we do not have a timeframe for when this effort would be prioritized at this time.
-
Verified Developer Badge Partners get a verified badge, it would be nice for published developers to get a badge too, maybe after a certain usage requirement of their extension, like how partners have to hit certain limits to become partner, maybe enough usages or page views of the extension will get a dev a badge.
163 votes -
Allow channel moderators to control polls/predictions over the API The endpoints announced earlier today ( https://discuss.dev.twitch.tv/t/announcing-apis-and-eventsub-for-polls-and-predictions/31539 ) should be usable by channel moderators so that third-party apps like Chatty can make use of them without the broadcaster needing to authenticate.
161 votes -
Live notification Kraken allows you to set Game and Title.
Helix allows you to set nothing.
Aside from updating Helix to allow setting game and title, we'd like to be able to set the "Go Live Notification"
155 votes -
Get the authenticated user's emotes (equivalent to existing Kraken endpoint) This Kraken endpoint provides the emotes a user has access to: https://dev.twitch.tv/docs/v5/reference/users#get-user-emotes
A similar functionality would be nice for the new API as well. It should contain all emotes a user has access to, for example Global Emotes, Subemotes, Bit Emotes, Emotes unlocked by Channel Points and so on (the Kraken endpoint is unfortunately missing some types of emotes).
The emotes returned would be for the authenticated user, with an appropriate scope required.
148 votes -
Create Clip enhancements When creating a clip via the Create Clip API, it is VERY limited compared to the (not for public use) GraphQL interface. Requesting that the following enhancements be made to the Create Clip API so that 3rd party apps can leverage them:
1) Add ability to specify the clip start time (number of seconds from when the broadcast started). Reason: when deciding when to create a clip, apps may want to look back 10-15 seconds instead of generating the clip starting from when the API is called.
2) Add ability to specify the clip title. Reason: currently, the API defaults…131 votes -
Provide API to return subscriber points As noted here
https://help.twitch.tv/s/article/lifetime-subscriber-guide-for-partners?language=en_US
Lifetime Subscribers are a unique benefit for Twitch Partners. Lifetime subscriptions do not generate revenue or additional subscription points.
No where in the subscribers API is a given sub tagged as lifetime.
So whilst we can math the subscriber points from helix, we can't discount these lifetime subs from our count.
Extend the subscribers API to flag as lifetime, (or provide a seperate endpoint)
And provide a API to fetch the Sub Points without having to iterate all pages.130 votes“points” has been added to the “Get Broadcaster Subscriptions” endpoint and documentation has been updated.
-
Please provide an API for the new "Unban Request" system So that third party developers can be notified of new unban request
And that third party developers can respond to those unban requests, the same way as you can on the moderator view129 votes -
Please make the suspicious users feature available to mods The new suspicious users feature should be available to third-party moderation tools.
A lot of moderators use third-party tools and it would be quite important to at least be able to see the messages/warnings. It would be even better if changing the restricted/monitoring state of a user would be possible as well.
This would be akin to the great AutoMod API, which provides mods with a PubSub topic for detailed real-time information and Helix endpoints for handling messages.
128 votes -
Include follow count in /helix/users Add follow count to /helix/users endpoint. This data is accessible via /helix/users/follows, but would require an additional call.
124 votes -
Delete clips There is no API methods for deleting a Clip
Please provide a method
110 votes -
Channel Points API: Grantable Control of Third-Party Rewards Based on the current channel points API, a client may only access/update rewards for their own custom rewards. However, for some moderation tools, I believe managing custom rewards created by other clients and/or the Channel Owner's Dashboard would be beneficial.
Take for example a reward such as "Hydrate!", where, after 10 minutes you want this cleared from the reward queue if it hasn't been actioned already. To do this with the current API, a channel owner would have to first delete the existing "Hydrate!" reward and then recreate it using the script client. Repeating this for every reward to be…
107 votes -
Subs Tenure in Helix We would like subs tenure in Helix in order to use this for merch extensions providing tenure-based merch options.
97 votes -
94 votes
-
Create Custom Reward: can't provide custom image Create/Update doesn't provide the ability to upload/change images for a reward.
This would be useful.
Alternatively if we can't do upload initially.
Add the ability to specify a channel emote (either by coDe or ID) so the reward would "copy" the channelEmote for that channel in.
So if I create a reward for CohhCarnage I can pick a cohhEmote (but I can't pick a liriki emote)
Or specify a URL to fetch a Image from
89 votes -
Show reruns in /helix/streams as type "rerun" Currently there's no way to get the status of a rerun stream, as /helix/streams only returns streams with the type "live" and "" (error)
Adding reruns with its type set to "rerun" would allow it to return rerun streams as well.
It's a problem that you can't get the status of a rerun stream because you then have no other choice than to treat it as offline, which means you e.g. may initiate a host, which will interfere with the stream.
84 votes -
Twitch Approved Developer Program - Reinstate Follow/Unfollow API Given the fact that Twitch had to take down the follow/unfollow api's due to bot programs that are out there - my suggestion would be to have an approved set of developers that propose and showcase their applications.
This way Twitch could bring back the follow/unfollow API and any service or developer that was in violation of Twitch's TOS regarding the API could be warned and ultimately have their access and credentials removed.
Twitch Developers could review the logs of which applications were connected with BOT services and immediately shut those down rather then removing the api in its entirety…
78 votes
- Don't see your idea?