436 results found

1. API to get per-user information about streamer support (gifts and bits)

   I'd like to see an API endpoint that gives me information about the level of support for a given channel/streamer and user/viewer combination.

   On one hand, I as a viewer want to have a way of getting my total numbers raised in support of a given streamer (that is, user BhaaLseN on $channel).

   On the other hand, I as a streamer want to have a way of getting total numbers raised by a particular viewer of mine (that is, user $viewer on BhaaLseN).

   The former is meant for viewers and addons like FFZ/BTTV that display numbers: amount of subs gifted (which is already shown in the "Gift a Sub" popup), amount of bits cheered (which is somewhat reflected in the Cheer popup and the bit badge, but doesn't appear as an actual number I think), plus perhaps even a culmination of the Wallet subpage (that could equate the number of subs/bits into actual money spent).
   This should be available to the user themselves, regardless of channel, and only return their own level of support (or value if you like).
   It could look like a simple GET request to /helix/channel_support/$channel to retrieve my own data for $channel.

   The latter is meant for both streamers and perhaps their editors/moderators (but at least channel bots) to allow them to get data on their loyal viewers that provide support over extended periods of time, and might be eligible for a little extra. Many streamers reward milestones with special giveaways and other personal goodies for those particular individuals. Most go by gift count (which can be viewed when gifting or using the gift badge), amount bits cheered (which is again from the cheer badge) or any combination thereof.
   This obviously shouldn't be available to just anyone except for the streamer, and maybe even to a trusted group of individuals per channel (editors, moderators and/or bots) to keep track of how much viewers spend on their channel, and also verify that what they claim is true.
   It could look like a simple GET request to /helix/channel_support/$channel/$viewer to retrieve data for $viewer on $channel, assuming that the current user has a minimum access level on $channel (such as moderator or editor). In case this remains limited to the channel owner themselves, the endpoint could obviously drop the $channel segment, but I'm also considering scenarios where roles other than the broadcaster may want (or need) access to this.

   The data should be there (after all, the former is somewhat available for viewers already using the Wallet page for both subscriptions and bits), it's just that there is no API available for it (aside from GQL I suppose, which developers may not use).

   I'd like to see an API endpoint that gives me information about the level of support for a given channel/streamer and user/viewer combination.

   On one hand, I as a viewer want to have a way of getting my total numbers raised in support of a given streamer (that is, user BhaaLseN on $channel).

   On the other hand, I as a streamer want to have a way of getting total numbers raised by a particular viewer of mine (that is, user $viewer on BhaaLseN).

   The former is meant for viewers and addons like FFZ/BTTV that display numbers: amount of subs gifted… more

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. hype train

   With the way how certain bots work, Webhooks wouldn't work with said bots. So my Suggestion is to include PubSub so more bots can utilize features like Hype Train and other stuff included on twitch.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Deferred  ·  1 comment  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. bad

   Where is all the information regarding --header 'Authorization

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Highlight vod offset/origin vod

   Extend the Videos API via a "metadata" endpoint, that provides additional data about the video.

   Including but not limited to

   • Category changes during the video
   • Offsets are relative to the source video that the video is from. So for a highlight it would report the video it was cut from and include where in the origin file the highlight is cut from.

   For Example: https://api.twitch.tv/helix/videos/metadata?id=1234
   Metadata would support up to 100 (or 50) id's at once like Get Videos

   Returns examples

   A video of type archive
   {
   "data": [
   {
   "id": "1234",
   "duration": 18000,
   "chapters": [
   {
   "offset": 0,
   "gameid": "200"
   },
   {
   "offset": 500,
   "gameid": "220"
   }
   ],
   parent: null
   }
   ]
   }

   A video of type highlight
   {
   "data": [
   {
   "id": "1235",
   "duration": 600,
   "chapters": [
   {
   "offset": 300,
   "game_id": "200"
   }
   ],
   "parent": {
   "offset": 200,
   "id": 4321
   }
   }
   ]
   }

   Use cases:

   • if we present a highlight on a third party website, when the video is complete, we can present a easy way to go to the next Highlight in the series (where highlights are cut sequentially) or easily link to the original stream archive for continued watching.

   This is an expansion of https://twitch.uservoice.com/forums/310213-developers/suggestions/38155990-return-tags-and-game-id-in-get-videos-in-helix

   Extend the Videos API via a "metadata" endpoint, that provides additional data about the video.

   Including but not limited to

   • Category changes during the video
   • Offsets are relative to the source video that the video is from. So for a highlight it would report the video it was cut from and include where in the origin file the highlight is cut from.

   For Example: https://api.twitch.tv/helix/videos/metadata?id=1234
   Metadata would support up to 100 (or 50) id's at once like Get Videos

   Returns examples

   A video of type archive
   {
   "data": [
   {
   "id": "1234",
   "duration": 18000,
   "chapters": [
   {
   "offset": 0,
   "game… more

   58 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Add Helper: Feature Flags from extension to the API for backend validation

   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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Include eventsub subscriptionevent user message

   Include subscription message with the subscription event to be consistent with how bits include messages in the event.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Add "Channel title" ingredient to IFTTT (If That Then This)

   Would be nice to if the Twitch service over at IFTTT had the channel title as an ingredient to be used.

   This would enable a huge range of services to utilize the channel title for marketing purposes.

   Zapier has this, but not IFTTT.

   Screenshot of ingredients:
   https://imgur.com/a/l4DJIsx

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Extend heix subscribers or provide another endpoint for Lifetime Subscriber data

   This guide descibes how Partners can assign someone a lifetime sub that doesn't count to rev of points

   https://help.twitch.tv/s/article/lifetime-subscriber-guide-for-partners

   The API doesn't present any information as to who is a lifetime sub or not.
   So we cannot guestimate sub points (or revenue if we are building revenue reporting tools for streamers we work with) from the API as we don't know who is a lifetime sub or not.

   Please provide an API endpoint that lists these subs, which would be "cheaper" than a boolean flag added to the subscribers endpoint

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Get Emotes Infos by emote id(s)

   Please can you provide an endpoint for get emote informations (like channel's id) with emote id(s), this can be usefull ?

   PS: Morever, datas returned by the Get all chat Emoticons endpoint API are not updated (here: https://dev.twitch.tv/docs/v5/reference/chat#get-all-chat-emoticons).

   Thanks you very much :),

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Pop up comment / follow or either any will show on my screen when streaming on mobile

    I agree all the privacy n rules here but I have a suggestion that I need a pop out comment / follow / donate or either subscribed notification while I am streaming with mobile I ha d high hopes for it

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Code in Sample 2 doesn't work, not even with freshly created credentials and app tokens.

    Code in Sample 2 doesn't work, not even with freshly created credentials and app tokens.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Add bet support to API (For Streamer AND Viewer)

    CRUD for bet as streamer
    CRUD for bet as viewer

    As streamer:

    • Being able to start/cancel a bet from endpoint
    • Being able to state who won from endpoint
    • Maybe get stats about the bet (invested coins, status, nb of participant, ...) (as Events or/and as HTTP API)

    As viewer:
    - Receive an Event when there is a new bet
    - Get bet info using endpoint (remaining time, title, bet A, bet B, nb of people who bet)
    - Place a bet using endpoint
    - Event win or lose

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Get Active Extension Version info

    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 which would list each version and have information about each, much like the dev dashboard Versions page.

    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… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Add query parameter option to make non-interactive frames more visually clean

    I have embedded my Twitch channel on my website as a non-interactive iframe in my side panel.

    Example:
    https://imgur.com/a/v1wc8ri

    However, there is so much text there which clutters the UI.

    By having my stream title there from when I was online does not add any value. It certainly does not promote my channel.

    I would much more prefer if I could just have the bare minimum there and I can show my own offline-image.

    Example:
    https://imgur.com/a/v1wc8ri

    It would be nice if we had a new query parameter option for embedding channels, which could remove any promotion texts or videos / aka make it more minimalistic, to only show the Twitch button and the channel's offline image.

    I have embedded my Twitch channel on my website as a non-interactive iframe in my side panel.

    Example:
    https://imgur.com/a/v1wc8ri

    However, there is so much text there which clutters the UI.

    By having my stream title there from when I was online does not add any value. It certainly does not promote my channel.

    I would much more prefer if I could just have the bare minimum there and I can show my own offline-image.

    Example:
    https://imgur.com/a/v1wc8ri

    It would be nice if we had a new query parameter option for embedding channels, which could remove any promotion texts or videos /… more

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Mature flag in get channels and be modifable via patch channels

    Similar to

    https://twitch.uservoice.com/forums/310213-developers/suggestions/38375011-mature-flag-on-get-streams-endpoint

    But for the Get Channel information endpoint

    We should also be able to modify the flag via the Set Channel Information endpoint

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. API to get Muting information about VODs

    Please provide an API and/or webhook/event sub

    That provides information about if a VOD/clip/other content is muted

    We will need the start/end time slots for each muting on the content

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. API to unpublish a vod

    Please provide or update the videos API to allow API users to unpublish a VOD

    14 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Add the total field to the helix/subscriptions endpoint

    Just like the /helix/users/follows endpoint, I would like the /helix/subscriptions endpoint to also provide the total results in addition to the next and previous links.

    Currently I have to recursively go through all the subscriber pages, 100 par 100, and add up for each one. So I make for my 12,000 subscribers not far from 120 calls which, on the one hand overloads the service and uses part of my call quota, and on the other hand take almost a whole minute to execute.

    This is a certain burden for our two sides, as a "total" field would solve all our problems on this endpoint.

    Just like the /helix/users/follows endpoint, I would like the /helix/subscriptions endpoint to also provide the total results in addition to the next and previous links.

    Currently I have to recursively go through all the subscriber pages, 100 par 100, and add up for each one. So I make for my 12,000 subscribers not far from 120 calls which, on the one hand overloads the service and uses part of my call quota, and on the other hand take almost a whole minute to execute.

    This is a certain burden for our two sides, as a "total" field would solve all… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Get the latest subscriber

    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 don't have more results or that's the last page. According to the docs, the pagination cursor should don't return anything in that case.

    Even If I use the pagination cursor to fetch ALL subscribers, with 100 results per page, it wouldn't be worth doing 10 calls if a streamer has 1000+ subscribers just to get the latest, for example, this would take A LOT of time to go through all those pages.

    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… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Authentication Docs Improvement

    Honestly this whole documentation is a bit sloppy. There should be clearer examples of using the APIs as I had to go Googling how the authentication actually works as the headers seem to be different than this suggests.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close