Translate Ideas and Comments
Choose language:
There was an error during translation

Developers

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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.

    116 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    127 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  6 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    50 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  4. For managing Bans without having to create an IRC connection and to remove the issue of running into the global message limit when banning large numbers of users or cleaning out a large banlist

    42 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Follow up to https://twitch.uservoice.com/forums/310213-developers/suggestions/39228787-extend-the-clips-api-to-include-recreation-from-so

    to request the offset of a clip being added to the API

    Use cases include

    • Deduplication of Clips submitted to a clips submission thing
    • Recreate the clip from a copy of the vod.
    • Using the offset to easily spot "hype" points of a stream for channel editors making highlights to focus on that point aka "heatmaps of popular stream time points"
    • From CSharpFritz: Show clips in the order that they naturally occurred, and not the time that they were created
    46 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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,…

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  7. With the removal of the Follow Create endpoint.

    A "non moderation bot" can no longer be automatically added to a channel.
    The owner of the bot would have to "login" to the account and manually follow the channel(s) the bot joins.

    A "non moderation" bot doesn't run moderation commands, so giving it "mod" wouldn't make sense. (Which would bypass the follow requirement)

    Please provide a way to "authorise adding a bot to a channel" that will auto follow the bot to the channel. For this purpose

    This could be similar to how Discord does bots, where to add a bot…

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Investigating  ·  5 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…

    101 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  9. If would be very useful for chat clients or chat overlays to be able to show live updates on these features. Currently they are only available for the broadcaster (redemptions) or not at all through websockets (polls/predictions).

    Ideally this would be available for all users to receive, just like chat is (which allows more simple integration into all kinds of tools), but even just mods using third-party moderation tools would already benefit greatly from this.

    I included all three of those features, since they all seem to follow the same idea of only allowing the broadcaster access to that information…

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  2 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 view

    111 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  9 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  13. Why is the share always 80% streamer and 20% developer? Would be way better if the developers could decide their extension percentage.

    If I sell an cosmetic item in my game ( on my website) for 5$ I get like 4.8$
    If I want to sell the same item on twitch I would need to sell it for 24$ to get 4.8$

    So as developer I have these options:

    • Don't use Bits -> Streamer receives 0$
    • Link to our website -> Streamer receives 0$
    • Make prices way to expensive -> nobody buys -> Streamer receives 0$

    So if you make…

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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)…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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

    60 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  13 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  16. Subscribe topic only broadcasts "new subscriptions"

    So when a subscription "expires" we don't get a "payment notification" for a Resub

    This is NOT a eventsub for the "chat notification" see https://twitch.uservoice.com/forums/310213-developers/suggestions/42008104-please-provide-an-event-sub-that-emits-sub-notifi for that

    58 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →

    I’m not clear on the use case for this. It seems like with a resub chat message notification and subscribe/unsubscribe events you should have the data you need.

  17. When viewers cheer, they use cheermotes and commonly emotes in their cheer messages. Unfortunately, the payload received from EventSub's channel.cheer callbacks only have the raw text as entered by the user, with no indiciation of which portions of that text are cheermotes nor emotes. Thus, I propose the following update to the callback payload, similar to the channel.subscription.message event, that passes along the data for both so that a consumer of EventSub can reconstruct the message:

    {
        "subscription": {
            ...
        },
        "event": {
            ...
            "message": {
                "text": "Rah Rah Cheer! cheerwhal1 Cheer100 notACheer101 finite6ThrowBall",
                "cheermotes": [
                    {
                        "begin": 16,
                        "end":
    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Consideration  ·  2 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  18. Extend EventSub subscriptions topic to include information about who gave the gift if it was a gift subscription.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Investigating  ·  6 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  19. The problem occurred after the release of an extension game i developed, where the viewers could spend channel points to obtain in-game currency. With over 6000 viewers, the chat became impossible to moderate as there were so many messages per second. This very simple option would greatly relieve the chat in such situations.

    E.g.: "is_highlighted" (defaults to true)

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  20. The addition of the Emote Library that is coming soon is a fantastic addition, this is great for solving the issue of disparity between partners and affiliates on emote variety, without undermining the parner program and is a fantastic compromise.

    I would like to suggest the addition to the Twitch API to allow for enabling and disabling of active emotes from the Emote library via a privlaged API call from a token with sufficient privlages through oAUTH.

    An example of the proposed usecase would be 4 API calls:
    -Activate Emote [Params: Emote ID, (Optional: Emote Slot)]
    -Deactivate Emote by ID…

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 27 28
  • Don't see your idea?