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

Developers

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

39 results found

  1. 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…

    164 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  ·  Admin →
  2. Add follow count to /helix/users endpoint. This data is accessible via /helix/users/follows, but would require an additional call.

    155 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

    13 comments  ·  API  ·  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…

    121 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

    13 comments  ·  API  ·  Admin →
  4. 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.

    110 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

    Declined  ·  3 comments  ·  API  ·  Admin →
  5. 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.

    108 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  ·  Admin →
  6. 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 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  ·  Admin →
    Declined  ·  Travis Brown responded

    We 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.

  7. Please provide an API to allow developers to create update and fetch the new "profile block" at the top of panels.

    IE the new Social links section and the new bio/description block

    73 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

    Declined  ·  9 comments  ·  API  ·  Admin →
  8. It would be useful to know

    whats emotes are in a given casters emote library

    And an API to manage auto on/off/swap active emotes from that library

    59 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  ·  Admin →
  9. Please provide a Helix endpoint for inbound and outbound host status/information

    and by extension a webhook

    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

    Declined  ·  4 comments  ·  API  ·  Admin →
  10. 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 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  ·  Admin →
  11. Including but not limited to.

    • Add new panel
    • Remove Panel
    • Update panel
    • Change order of panels
    39 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

    4 comments  ·  API  ·  Admin →
  12. 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 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  ·  Admin →
  13. 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 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  ·  Admin →
  14. Endpoint to check if userID has a known bot or verified bot flag.

    Which currently exists as a undocumented v5/kraken endpoint.

    usercase: what rate limit does my bot have? I can check if my bot has mod but I can't check if my bot has verified bot.

    18 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

    Declined  ·  2 comments  ·  API  ·  Admin →
  15. When streamers run ads, they'd like to know how long the PreRolls are disabled for.

    Please extend https://dev.twitch.tv/docs/api/reference#start-commercial to return preroll data

    For example

    {
    "data": [{
    "length" : 60,
    "message" : "",
    "retry_after" : 480
    }]
    }

    becomes

    {
    "data": [{
    "length" : 60,
    "message" : "",
    "retryafter" : 480,
    "preroll
    ends": unixTimestamp
    }]
    }

    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  ·  Admin →
  16. Turning this off is really weak. How is X, a much larger platform able to do this? Youtube? Everyone else?

    4 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

    Declined  ·  0 comments  ·  API  ·  Admin →
  17. 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 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  ·  Admin →

    The 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

  18. Add support for RFC8252 (https://datatracker.ietf.org/doc/html/rfc8252#section-7.1) which allows for users to specify custom scheme URI's for OAUTH callback urls. This would allow native application developers to not have to piggyback through a server and instead they can configure their applications to handle these schemes for confirming the oauth callback, for example my-app-name:/authorization?code=XXXXX

    4 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  ·  Admin →
  19. Cheering Bits is the most famous way to support a streamer. However, it can be somewhat challenging for new users to get familiar with the Twitch Chat commands to properly do so.

    I propose an API which allows to trigger a regular cheer.
    This call obviously should not be signed instantly, but sandboxed where the Twitch backend requires a "Yes / No" response via GUI from the user.

    I think this can improve the user experience a lot and it can also improve the general usage of Twich Bits.
    For instance, many streamers use overlays in their stream to react…

    4 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

    Declined  ·  0 comments  ·  API  ·  Admin →
  20. Many times, "viewer_count" response field doesn't change during several minutes (due to caching?). However, when you're watching a stream you can see how this data is refreshed each 20-25 seconds.

    Benefit: Increase the precision of apps that use this field

    4 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

    Declined  ·  3 comments  ·  API  ·  Admin →
← Previous 1
  • Don't see your idea?