369 results found
-
Create API endpoints for Ads and the Ads Manager With the heavy push Twitch is making to have streamers use the Ads Manager and to run more ads in general, this could go a long way to making that easier on our end. Ideally we should be able to get the following information and do the following things:
- see how long until the next ad
- see whether or not pre-rolls are disabled and for how long
- see how many snoozes are left
- see the cooldown time until another ad can be run
- activate a snooze
- run an ad manually (this is already possible, but adding for completion)
Additionally, EventSub…
89 votes -
Pinned messages API Please provide an API to
- pin existing message
- pin a new message
- unpin a message
Which should work using a moderators token in line with the announced new feature
72 votesWe're planning to add support for pinned messages in the API and EventSub.
-
Offer a way to better handle app authorization on password reset One of the annoyances of the current authorization system is that whenever the broadcaster change their password, they need to reauthorize all apps as well, so developers need to have a way of warning the user to reauthorize it, or they will lose access to its features.
I understand this is a security feature, but it would be good if that could be handled separately, because a lot of times people just want to change password, and not revoke auth for third party apps
16 votes -
Search streams by Tag name Hey, not sure if this has been posted as a uservoice already, I took a quick glance using the above title as a query and couldnt find anything about it.
It would be nice with the new Custom Tags feature that we would be able to get a list of streams with x tag(s) for 3rd party use. Id envision this to either be its own endpoint, or potentially added to the
queryproperty of the "Get Streams" endpoint, like Kraken used to do with title searching (Which also would be nice to have back in Helix)30 votes -
Add/Remove Channel Editor via API Please add the ability to add/remove channel editors via the API. This was requested previously and marked completed but as far as I can tell it's not completed.
12 votes -
Raid Now If you have a created a raid.
You should be able to use the API to trigger "raid now"
Which is a button on the front end UI which allows the streamer to skip the 90 second.
52 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.
157 votes -
restrictions to prevent bot follows The idea is simple: Add the same phone & email verification options to the ability to actually follow a channel, and thus also giving account age requirements to be able to follow a channel. This will allow small streamers being targeted by hate raid Bot attacks to simply prevent the bot attacks easily, instead of being driven off the platform.
65 votes -
Extend the "ban user" endpoint to accept "login" as an alternative to the already existing "user_id" Today when you're using chat you can just enter
/ban userand the user will be banned, and the same is true for the IRC command, you can ban just by their username. It would be good if the ban endpoint would follow the same pattern.The use case for that is that I have a tool to mass-ban multiple users on multiple channels at the same time (I mod quite a lot of channels, so this streamlines this process), and I decided to migrate from the IRC API to the helix API, but because of it just accepting the…
16 votes -
Disable clip creation Right now if we want to disable/enable clip creation we kinda have to play hide and seek in the dashboard.
It's good to have that possibility, but it doesn't answer emergency cases.It happens to streamers that they leak more or less critical personnal info (address, credit card, real name...). In such case, most of the viewers will create a clip to watch it back and by the time we find the option on the dashboard it's way too lat to disable clips creation.
Also it wouldn't totally solve it, having an API would help mitigate such kind of leak…
5 votes -
Indicate on GetUser endpoint if he/she allows raids A streamer can configure if he/she allows to send a raid to his/her channel or not. But this information can't get using twitch api endpoint. The only way is trying to send a raid, and check if any error is returned or not.
Add this information directly in twitch API can helpful to select a streamer to send a raid.
19 votes -
Allow bots joining Guest Star, capturing, and sending audio I have a Discord bot that can read audio from participants and individually transcribe their speech to text and display it on the stream. I have another Discord bot that can synthesize Twitch chat messages (TTS) and send the utterance to voice channel participants. Would like to be able to do the same through Guest Star, especially since Guest Star has alledgedly better audio quality.
Thank you!
6 votes -
WebRTC Streaming (e.g. from a web app) There is already WebRTC support, but it is not yet public. (see https://99.181.116.152:4443/health and https://99.181.116.152:4443/offer ) But I would really like it to be public so I can integrate streaming directly into my web application. The API for the current implementation, named "webgest", a module of "intelligest", is not publicly documented, only mentioned once here: https://blog.twitch.tv/en/2022/04/26/ingesting-live-video-streams-at-global-scale/ ; and the other two URLs I linked earlier do not work with my stream key (probably only works with a different set of stream keys used for development?) But in any case, I am now forced to use alternative third-party streaming platforms which…
5 votes -
[BUG] API does not allow to remove custom tags According to the recently updated documentation (https://dev.twitch.tv/docs/api/reference/#modify-channel-information ):
To remove all tags from the channel, set tags to an empty array.However that does not work at all, as the API returns:
{"error":"Bad Request","status":400,"message":"The request must update at least one channel property field."}
When receiving the following payload:
{"tags": []}
If you send the following the title gets updated and the tags remain untouched:
{"title": "Test ing the API", "tags": []}
4 votes -
Modify EventSub's channel.follow to include shoutout info Within EventSub's channel.follow event, it would be nice if there was info about if the follow originated from a Shoutout, and who the Shoutout was from.
This would be useful for stream overlays, so the notification can say something like "[Viewer] followed, thanks to [Shoutout Origin]'s shoutout!"
9 votes -
Add "first-time chatters" filter to chat settings endpoint The following endpoint allows to get/set the chat un emote/sub/follow-only....
https://dev.twitch.tv/docs/api/reference#get-chat-settings
https://dev.twitch.tv/docs/api/reference#update-chat-settingsI believe it would make sens to add the new "first-time chatter" filter brought by shield mode to it so external tools can get or set this value.
5 votes -
Add Optional OAuth Scope Selection to Authorize Page In order to give the end user more control, applications may be developed to have dynamic scopes, which currently is on the third-party developer's side to manage, such as providing a list of checkboxes to determine which permissions to grant.
I suggest adding a parameter to <id.twitch.tv/oauth2/authorize> to turn the listed permissions into checkboxes, and only the checked permissions returned in the scope list that accompanies the resulting token. This will make the user's interaction with the permissions feel more seamless, as well as prevent "backouts" when the user is presented with a list of access permissions they can't "un-choose".3 votes -
Re-add created at, streak and/or expires to Check User Subscription In Twitch v5, the Get User Subscription endpoint contained a created_at and a streak for the current user subscription for a broadcaster.
Helix, lacks this functionality, and thus it is impossible to determine how long someone has been subscribed for, and also impossible to determine if they've renewed their subscription.
These fields are imperative to some applications, especially ones that want to externally reward members monthly for each month they've subscribed. Please return these fields to the endpoint!
32 votes -
Monitor and Restrict User commands as API endpoints 4 chat commands that would be great to have as API endpoints:
/monitor USERNAME - Start monitoring a user's messages.
/unmonitor USERNAME - Stop monitoring a user's messages.
/restrict USERNAME - Start restricting a user's messages
/unrestrict USERNAME - Stop restricting a user's messages10 votes -
Allow Channel Editors to use Helix Raids API With the new Raids API, it should mirror IRC where channel editors can trigger raid/unraid. Currently, this is not supported (need broadcaster user access token). Until this functionality is added, I will not be migrating to Helix Raids
14 votes
- Don't see your idea?