Skip to content
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

436 results found

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

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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…

    33 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Please extend the error message of the start commercial API to be more useful

    Current response is

    { error: 'Bad Request',
    status: 400,
    message: 'channel for id "SOMEID" has recently ran a commercial' }

    It should return the retry_after remaining value

    6 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Topic.

    Cannot control highlight message/unlock emote rewards to enable/disable/change price or even list them etc via this API

    3 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

    3 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. What's been made available for the events from PubSub is nice, but currently there is no way to know of when a unfulfilled reward has been marked as complete by a Streamer/Mod. Since the event is already well structured, all that would need to be done is simply re-send the same event with the status property updated to reflect that it was fulfilled (either just using the existing "FULFILLED" value or possibly a new value like "MANUALLY FULFILLED").

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Currently the API doesn't support marking a reward out of stock manually. This may be beneficial for rewards that take some time to process where specifying a hard cooldown wouldn't be appropriate.

    In addition, support for a custom "out of stock" message may benefit some developers. Using sound alerts as an example, if a streamer is in "focus mode" and needs to concentrate on what they are doing, rather than say the default "out of stock" it could say "StreamerX is focusing right now".

    3 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Add an endpoint the returns a list of the latest cheers to a channel. The list should include: username, bits, message and date-time.

    31 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Code in Sample 2 doesn't work, not even with freshly created credentials and app tokens.

    2 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

    Planned  ·  0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow developers to mock responses from all common integration points- subs, bits, follows, streams, etc, and allow users to mock users as well.

    This is useful for automated testing as well as building extensions.

    5 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. It is useful to know if a streamer is on the home page.

    Both from a

    • internal (to the channel) statistical standpoint
    • as a moderation standpoint (we are on the home page we should up the follow limit to avoid trolls or lower the follow limit to let people chat).

    Please provide a way to

    • determine if a given channel is on the homepage (by region)
    • which slot it is in on that region

    And if possible

    provide this information has a webhook so we don't have to constantly poll for this information

    Additionally we may use it as a…

    8 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    3 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 74 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. In order to send a chat message via https://dev.twitch.tv/docs/extensions/reference/#send-extension-chat-message you need to know the current active version of your extension. There's no way to retrieve information about your extensions' versions.

    There's one way which is kind of roundabout, by first using /extensions/${CLIENT_ID}/live_activated_channels to get a list of users, then using /helix/users/extensions/list on one to find the extension again and get its version there.

    This could be much quicker to find if live_activated_channels had a version field with the live extension version (it only ever returns a list of channels using the live version).

    There could also be a /extensions/${CLIENT_ID}/versions endpoint…

    2 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Add the ability to trigger a reward redemption from the API - similar/same to what happens when clicking the reward in the chat dialog.

    For example an extension has added a custom reward XYZ and to trigger a certain action in or for the extension this reward needs to be used.

    So instead of the extension telling the viewer "please redeem reward XYZ to do this or that" and then waiting for the redemption, immediately trigger the redemtion via the API - saving the viewer the need to browse and look for the redemtion in question.

    Result of this API…

    3 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Old Twitch v5 API has an endpoint called "Get Top Clips" (https://dev.twitch.tv/docs/v5/reference/clips#get-top-clips)

    I think the new API should also include this endpoint because the current way of getting the top clips is not exactly the most user friendly one. Currently if you want to get top clips, you need to get all clips using the "Get Clips" endpoint and then sort them out manually on our side. This works if you know exactly what you want. For example if you want top clips for a game you can use the game parameter.

    Unfortunately this isn't the most optimal…

    6 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Right now, you can only check if the streamer setup permissions for your extension from the helper, such as isBitsEnabled, isChatEnabled, isSubscriptionStatusAvailable. It would be nice to be able to query the API to see which permissions the streamer setup.

    1 vote

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. The endpoint /helix/subscriptions?broadcaster_id=USER_ID doesn't return the data from the most recent to the oldest subscriber.

    We could maybe use /helix/subscriptions/events?broadcaster_id=ID but the data here apparently doesn't last more than 5 days or so. This doesn't work for small streamers who don't have a lot of subscribers coming on a daily basis, for example.

    Suggestions:

    1. Create an "order" parameter to the first endpoint, so we could use like /helix/subscriptions?broadcaster_id=USER_ID&order=desc&limit=1
    2. Make the second endpoint return the latest "forever".

    The first endpoint seems buggy, the data being returned comes in random order and the pagination cursor is always present, even if I clearly…

    2 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. When a reward is created by the API, we should be able to prevent the streamer from being able to change values that we set. They should still be able to disable or delete the reward.

    By locking the reward, we can offer a similar experience to all users and prevent confusion when one reward is drastically different from the same reward on another stream.

    Just some use cases below would benefit from this.

    Currently, we can set the max number of users of a reward per stream and our backend could be enforcing the same amount of rewards redeemed.…

    3 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Submitting this on behalf of Jeff Fritz, which he mentioned while talking about a Channel Points streaming opportunity. I was talking about building an example that uses webhooks to flag when a specific category is selected for a stream so a developer knows when to enable or disable a channel points reward. His question was why Twitch doesn't handle that automatically.

    If there was an optional category property that could be set when creating the custom reward, Twitch could potentially handle enabling/disabling a reward more reliably if the context for switching is a category update, which would probably be the…

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Having written one and a half client libraries for IRC now, I wish Twitch Chat was exposed over a more consistent protocol.

    • Allow read-only access to chat messages (and other related live data and events) via PubSub, with clean re-designed JSON Chat message payloads
    • No longer identify channels and users by their login name, use user IDs for all purposes
    • Send messages via an API call

    Most importantly, I would expect a redesigned API to think of edge-cases in a better way than IRC currently does. For example, what happens on IRC if a channel gets suspended, or a channel…

    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

    0 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?