366 results found
-
Latest cheers API endpoint Add an endpoint the returns a list of the latest cheers to a channel. The list should include: username, bits, message and date-time.
30 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!
29 votes -
"Get Users Follows" with follower's account creation date The v5 endpoint contains the follower's account creation date, the new endpoint (https://dev.twitch.tv/docs/api/reference#get-users-follows) does not.
Knowing when a follower created their account is very useful to moderators monitoring recent follows to keep an eye on potentially problematic users (new account could mean a previously banned user returning) or to detect mass follows from bots (which often have a similar account creation date). Monitoring recent follows is especially useful in follow-only chat mode.
While it is possible to get the account creation date from the "Get Users" endpoint (https://dev.twitch.tv/docs/api/reference#get-users) and then merge it with the follower data,…
29 votes -
Extension webhooks for streamer actions For the purposes of GDPR it would be useful to have the following webhooks:
- When a Streamer installs an extension
- When a streamer activates an extension
- When a streamer deactivates an extension
- When a streamer uninstalls an extension.
The most important one is the uninstall, it allows us the third party to be notified of an uninstalled.
The Shopify platform has this with the rule that a third party should, automatically delete all Store (and that stores customer data) 30 days after that hook triggers.
We need/should do the same, delete any broadcaster, or broadcaster viewer (and subscribers) data 30…
28 votes -
Gifted Sub Leaderboard Similar to the Bits Leaderboard, please add a gifted subs leaderboard API, so we can see everyone who has gifted a sub in the channel.
28 votes -
API to CRUD panels for streamers Including but not limited to.
- Add new panel
- Remove Panel
- Update panel
- Change order of panels
25 votes -
Add endpoints to set and retrieve moderator comments for a user See https://blog.twitch.tv/channel-moderation-tools-in-chat-4188af21dbf9 for details.
24 votes -
Manage Roles via the API It shouldn't be required for manage roles such as mod/vip via the chat
It shouldn't be required to manage editor/mod/vip via the roles manager
it would be useful for automation/third party management to be able to manage roles via the API
21 votesCurrently not a top priority, but we are interested in your use cases for this functionality to be considered at a later time. Please include more information in the comments as to how and why this would be useful.
-
Add subscriber only status to Streams API endpoint. Right now there is no official way (there is an undocumented endpoint) to determine whether a stream is sub only or not. Subscriber only status prohibits a lot of people from interacting with the stream, so it'd make sense for applications to be aware of such a state.
21 votes -
IRC Request: Follow tag to filter out non follower messages Currently, it is easy to tell if a user that sent a message in a streamer’s channel is a subscriber, VIP, or moderator of that channel. However, there is no way to tell if that user is a follower of the channel.
With the rise of hate raids and malicious messages, I want to ensure that if a streamer is using a chat box overlay, that they have the option to only let messages from followers appear. Malicious users usually don’t follow the channel, and so this will prevent their messages from appearing on stream.
I do understand that this…
20 votes -
Subscriber start date Add subscriber start date to get broadcaster subscriptions endpoint
19 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)18 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.
18 votes -
Extend Moderation API to retrieve and set mod comments of a defined user An update on Jan 31, 2019 gave channel moderators the ability to add comments to users within chat. There is currently no way to use the API to be able to set or retrieve comments for users in chat.
This should be available to the broadcaster and all moderators within a channel.
To add a mod comment to a user, the endpoint could take the following data as inputs:
- User: {user's name}
- Moderator: {mod's name}
- Broadcaster: {broadcaster's name}
- Comment: {comment to be applied}On success, this would return the following:
- Success: {true}
- date: {date}…18 votes -
Channel Points for bots without API Hey. I know that people are requesting API for Channel Points. But I came up with better and easier idea.
When streamer creates new reward in dashboard, there should be option to "run a link" in background after reward is redeemed. This type of button will trigger bot with GET-request and bot will run specific action.
Why I think this approach is better than API:
1. No API on Twitch side, obviosly.
2. Bots won't be abble to control Channel Points directly.
3. This will work with any bot who will support this kind of triggers.
4. Easier to use…18 votes -
Followed categories API It's possible for a third-party app to query a user's followed channels, but not followed categories. This is a very useful tool for creating alternate views to a follow list
Use-case: Raid recommendation tool - it compares channel stats to your own and recommends those that are most similar, and also those you haven't recently raided. To do this, it needs to start with a list of everyone you follow who's live, and then does further research.
17 votes -
Make rate limit headers available to CORS / client-side requests Currently the rate limit headers "ratelimit-reset", "ratelimit-remaining" and "ratelimit-limit" are not accessible on browser / cors requests due to browser restrictions.
I request that Twitch adds the "Access-Control-Expose-Headers" header on the helix endpoints so that tools running in a browser can follow the rate limits without guessing if they are still within the limits or having to watch for 429 HTTP codes.17 votes -
Lookup User by Display Name Add a "/users"-like API method that supports display names. This will let bot commands which have a username parameter support Asian-family character display names to be passed the same as Roman-alphabet channel names. It will also let systems verify that a provided name (channel or display) exists on Twitch, and merge any information for a user's display name with the information for that user's channel name, to prevent "duplicate" sets of data: one for the display name; one for the channel name.
16 votes -
Expose Games/Chapters on the Videos API There's currently no way to view the games/chapters on a video. This would be very useful for an application I'm building
16 votes -
Include more fields in Get Global / Channel Chat Badges endpoints In the new badge-related endpoints, badge objects in returned sets contain only their IDs and URLs, which compared to the only existing alternative (undocumented badges.twitch.tv endpoint announced in twitchdev forums[1]) isn't enough for things like custom chat clients that are very popular among many Twitch users.
Ever since that undocumented endpoint came to existence, we've been using it in our chat client and would at least need "description" and "title" properties that are present in badges.twitch.tv to display information about badges properly and replicate webchat's behavior. I believe both APIs use the same internal data (at least for Global Badges)…16 votes
- Don't see your idea?