7 results found

1. Extend Clips API to provide the MP4 url so editors can automate downloads

   If I have an oAuth that represents a User, where the User is either

   • the broadcaster the clip is of
   • an editor of the channel that the clip is of
   • the user is the owner of the clip

   And I make a request for a Clip as documented: https://dev.twitch.tv/docs/api/reference#get-clips

   (but with the bearer naturally)

   The JSON Response should include the direct link to the MP4 or an ability to download the Clip.

   This is off the back of the removal/deprecation of some undocumented API's that I was using to get the MP4 URL for automated download for creation of clip reels and similar.

   If I have an oAuth that represents a User, where the User is either

   • the broadcaster the clip is of
   • an editor of the channel that the clip is of
   • the user is the owner of the clip

   And I make a request for a Clip as documented: https://dev.twitch.tv/docs/api/reference#get-clips

   (but with the bearer naturally)

   The JSON Response should include the direct link to the MP4 or an ability to download the Clip.

   This is off the back of the removal/deprecation of some undocumented API's that I was using to get the MP4 URL for automated download for creation of clip… more

   306 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

   Investigating  ·  10 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

2. Gift sub grouping

   When a "gift bomb"

   there is no way to gather all the gifts into one event.
   Each gift in a bomb should have a ID to link it to the header event.

   IRC sends a header saying "x is giving out y subs to the community"
   But the USERNOTICE events, don't say they belong to that event.

   Please provide a way to group the events, something as simple as a "parentid" in the child gifts subs, that'll link to a "childid" in the header event.

   This header and extra ID's need to be provided on the PubSub event feed for subscriptions as well.

   It might be beneficial to include on webhooks, but Helix doesn't only provide if it a given gift was part of a bomb or not.

   When a "gift bomb"

   there is no way to gather all the gifts into one event.
   Each gift in a bomb should have a ID to link it to the header event.

   IRC sends a header saying "x is giving out y subs to the community"
   But the USERNOTICE events, don't say they belong to that event.

   Please provide a way to group the events, something as simple as a "parentid" in the child gifts subs, that'll link to a "childid" in the header event.

   This header and extra ID's need to be provided on the PubSub event… more

   73 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
   Investigating  ·  Adminecressey (Admin, Twitch) responded

   We are investigating this for EventSub.

3. Stream title searching

   "The v5 endpoint searched for the channel title and category. Use “Search Channels” to match channel name or title." on https://dev.twitch.tv/docs/api/migration is wrong because the new API does not matches the title! There is no replacement for title searching!

   43 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

   Investigating  ·  7 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

4. Bot auto follow a channel

   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 to a server, you need an oAuth flow, and then on compleition of that flow lets the bot in the server.

   So in this example, I login as barrycarlyon I grant the bot access to my channel using scope "bot:allow" this auto follows that bot to my channel.

   So the "follow" is initated from my website and the channel authenticating in.
   And I've authenticated "my bot" to my clientID, and the target channel to my clientID.

   This essentially sets it up, so that the destination channel triggers the follow.

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

   37 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

   Investigating  ·  12 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 image_format or is_animated field to helix Emote endpoints

   With the addition of animated emotes there is no way to tell from the emote API responses of GetChannelEmotes and GetEmoteSets if a new emote ( id starting with "emotesv2_") is a normal emote or an animated gif emote without downloading it and checking the file contents.

   Would be nice to have either a "format" field that tells you "png" or "gif", or at least a "is_animated" bool field for each emote.

   Use cases: Whenever you wanna show emote stats or emote info for a channel (like in a chat clients or stats website or emote panel) you often wanna count and display animated sets separately but currently the only way to tell is to actually download the /v2/ files and check the type.

   With the addition of animated emotes there is no way to tell from the emote API responses of GetChannelEmotes and GetEmoteSets if a new emote ( id starting with "emotesv2_") is a normal emote or an animated gif emote without downloading it and checking the file contents.

   Would be nice to have either a "format" field that tells you "png" or "gif", or at least a "is_animated" bool field for each emote.

   Use cases: Whenever you wanna show emote stats or emote info for a channel (like in a chat clients or stats website or emote panel) you often wanna… more

   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
   Investigating  ·  AdminJon Bulava (Developer Relations, Twitch) responded

   We will be updating the documentation to make it clearer that the image in the payload will always be a static image. We are also planning to document the URL schema for the CDN to retrieve the animated version.

6. Helix Create Poll endpoint doesn't actually allow additional votes for polls.

   The Create Poll endpoint has optional query parameters to allow additional votes using either bits or channel points.

   However, it doesn't actually allow multiple votes. This can be seen in the pubsub response which explictly states that "multi_choice" (property indicating whether additional votes are allowed) is not enabled.

   When creating a poll through the web interface, it works just fine as it is created through the GQL and not the API. The GQL message also has an additional property to explicitly allow additional votes, on top of the properties that are used to either allow additional votes by bits and/or channel points.
   So either the query parameter is just not documented... or the endpoint itself is flawed because like half of its functionality is just broken.

   Also gonna drop the documentation link as a reference: https://dev.twitch.tv/docs/api/reference#create-poll

   Feel free to hit me up in case you want additional information regarding this (or when I just overlooked/misunderstood something)

   The Create Poll endpoint has optional query parameters to allow additional votes using either bits or channel points.

   However, it doesn't actually allow multiple votes. This can be seen in the pubsub response which explictly states that "multi_choice" (property indicating whether additional votes are allowed) is not enabled.

   When creating a poll through the web interface, it works just fine as it is created through the GQL and not the API. The GQL message also has an additional property to explicitly allow additional votes, on top of the properties that are used to either allow additional votes by bits and/or… more

   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

   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
   Investigating  ·  Adminecressey (Admin, Twitch) responded

   Thank you for reporting this issue. We will investigate.

7. GetChannelEmotes does not return GIF URL's

   The new GetChannelEmotes endpoint does not return the correct image url for gif emotes.

   For example on Lirik:

   for an animated emote it returns the url:

   https://static-cdn.jtvnw.net/emoticons/v1/emotesv2_53ff77f7c67641528739780d90568494/1.0

   When in fact the correct url should of been:

   https://static-cdn.jtvnw.net/emoticons/v2/emotesv2_53ff77f7c67641528739780d90568494/default/light/1.0

   At the moment all gif emotes are given png url's.

   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

   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
   Investigating  ·  AdminJon Bulava (Developer Relations, Twitch) responded

   This is the intended behavior. We will be updating the documentation to make it clearer that static images are returned and we will also be documenting the CDN URL schema to request different aspects of the emote (e.g. static/animated, light/dark/, etc)