770 results found

1. Create API endpoints for Ads and the Ads Manager

   With the heavy push Twitch is making to have streamers use the Ads Manager and to run more ads in general, this could go a long way to making that easier on our end. Ideally we should be able to get the following information and do the following things:

   • see how long until the next ad
   • see whether or not pre-rolls are disabled and for how long
   • see how many snoozes are left
   • see the cooldown time until another ad can be run
   • activate a snooze
   • run an ad manually (this is already possible, but adding for completion)

   Additionally, EventSub subscriptions for both ads being run and the ad break notification would be incredibly helpful. For example, chat bots would be able to display a message indicating when an ad break starts along with a message about why and how to sub/get turbo to prevent seeing them in the future. This would also allow accurate stream overlays to display a message on stream so that viewers who aren't seeing the ads understand why the streamer might be taking a break or waiting to answer questions.

   This would also help people who stream things such as speedruns where they're much less flexible with incorporating ads into their downtime. With this information, tools could be built that either snooze an ad or intelligently run ads of an appropriate length during known slower parts of a run, such as cutscenes, instead of the chance of it happening at a more frustrating time.

   With the heavy push Twitch is making to have streamers use the Ads Manager and to run more ads in general, this could go a long way to making that easier on our end. Ideally we should be able to get the following information and do the following things:

   • see how long until the next ad
   • see whether or not pre-rolls are disabled and for how long
   • see how many snoozes are left
   • see the cooldown time until another ad can be run
   • activate a snooze
   • run an ad manually (this is already possible, but adding for completion)

   Additionally, EventSub… more

   90 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

   3 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. Helix modify channel information endpoint should allow access to editors

   The new helix endpoint to modify channel information ( https://dev.twitch.tv/docs/api/reference#modify-channel-information ) doesn't work with a user token from a user that has been added as an editor to the channel. This basicially shuts out any clientside tool used by editors where it's impractical for the broadcaster to directly authorize access. Editors should be trusted enough to be able to choose their own tools.

   Allowing access to editors would especially make sense if this is intended as a replacement for the v5 endpoint ( https://dev.twitch.tv/docs/v5/reference/channels#update-channel ), which does allow editors to update the stream title and game. It would also work better together with the replace stream tags helix endpoint ( https://dev.twitch.tv/docs/api/reference#replace-stream-tags ), which also allows editors access.

   I would appreciate it if this change could be made to allow tools to continue working when switching to helix.

   The new helix endpoint to modify channel information ( https://dev.twitch.tv/docs/api/reference#modify-channel-information ) doesn't work with a user token from a user that has been added as an editor to the channel. This basicially shuts out any clientside tool used by editors where it's impractical for the broadcaster to directly authorize access. Editors should be trusted enough to be able to choose their own tools.

   Allowing access to editors would especially make sense if this is intended as a replacement for the v5 endpoint ( https://dev.twitch.tv/docs/v5/reference/channels#update-channel ), which does allow editors to update the stream title and game. It would also work… more

   86 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

   6 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

3. Expose profile accent color in the Users API

   In the channel settings, you may specify a "profile accent color" to represent your brand.
   Right now, this isn't exposed in the API at all.

   82 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

4. Revise the `channel.subscription` topics

   Request

   Organize channel.subscription topics to allow for alert like notifications to properly be provided. What displays in chat should be able to be mimicked via EventSub topics without having active tracking or additional api calls; Provide missing data where needed; Create new topics to fill in the gaps.

   ---

   Current Scenarios

   Brand New Subscriber: If a user subscribes for the first time in the channel, we get an alert as soon as they sub. This is incidental that it works properly for stream based alerts, as we are actually receiving the payment transaction rather than the in chat event.

   Prime Gaming Resubscriber: If someone resubscribes with Prime Gaming, we get not only the channel.subscription.message when they decide to share the message in chat, but also the channel.subscribe event as they are technically a NEW subscriber when they first click the button to resubscribe. As it was explained to me, this is because the subscription lapses usually before they are able to share the renew event in chat. So we get the event for subscription start, as well as the message event when they do decide to share it. Without active tracking up to days before the event looking for channel.subscription.end there is no way to properly react to the subscription alerts in a stateless manner.

   User Gifts a Sub: We receive a channel.subscription.gift event which is expected, but have no way to link to who gave which sub nor which channel.subscription.gift event was its pair. Explained more thoroughly here: https://twitch.uservoice.com/forums/310213-developers/suggestions/43813413-provide-a-gift-event-id-in-the-channel-subscribe

   User updates/upgrades their subscription: Currently in the case of PubSub no notification is sent for someone continuing their subscription from a gift or at times changing their tier to higher/lower. Data inconclusive of what happens in EventSub. https://twitch.uservoice.com/forums/310213-developers/suggestions/42454273-subscriber-upgrades

   User resubscribes automatically, but never shares: It is perfectly fine for a user to not share their resubscription event in chat as often times it is automatic when they do renew; however, for metrics such as goals or otherwise this data is crucial for accurate tracking. Explained more by Barry: https://twitch.uservoice.com/forums/310213-developers/suggestions/42008110-please-provide-an-event-sub-that-emits-resub-paym

   ---

   Important Notes

   The events should be "stateless", meaning that active tracking of subs that expire should not be needed to ensure correct event usage. Otherwise, this requires a server like runtime which defeats the future "transport agnostic" approach and would require a server. Chat like notifications should be able to be built from eventsub without long term tracking, or other API calls; such as listening for subs, cheers, point redeems etc. Out of this list of proposals below, the only events that are intended to be used in an alert/stateless like environment are channel.subscription.message, channel.subscription.gift, and channel.subscription.update. While the others can be used, the data would not be as transparent as to where it came from as it isn't provided in chat which may confuse viewers if used in that fashion.

   ---

   Proposal

   channel.subscribe Changes

   • channel.subscribe would become channel.subscription.begin (or.start) to fall inline with other EventSub topics as well as to give a more granular expression of what it reacts to.
   • Subscriptions starting up, that either are new or have lapsed in the channel, would be signaled here. In theory this would present no change to the current implementation, but should be documented that this should be used for metrics rather than alerts.
   • duration_months for multi month subs could be useful here to determine if a "long" term sub ended.
   • Gifter info to provide better metric data (more than just is_gift), would allow better understanding of retention.

   channel.subscription.message Changes

   • channel.subscription.message provide a mimicked data stream of what would appear in chat, meaning re-subscriptions or new subscriptions. The documentation would be also need to be changed to reflect this.
   • New Subscriptions
     • A "default" message object would be provided, meaning that the message.text would be an empty string (not null) and the message.emote array would be an Array.empty
     • cumulative_months as well as streak_months would be 0.
   • Gifting info would also be needed
     • is_gift:boolean - Indicates if the subscription was a gift. Default: false
     • is_anonmyous:boolean - Indicates if the gifter was anonymous. Default: false
     • gifter_user_id:string - User id of the gifter. Default: string.empty
     • gifter_user_login:string - User login of the gifter. Default: string.empty
     • gifter_user_name:string - User name of the gifter. Default: string.empty
     • gift_subscription_id:string/Guid - Id associated with the channel.subscription.gift event. Default: string.empty

   channel.subcription.end | Changes

   • channel.subscription.end is for expiring subscriptions. This in theory should provide no change per se in use, but data such as what was documented in the "channel.subscription.begin changes" would be beneficial here as well.

   channel.subscription.gift | Changes

   • When referencing the change mentioned earlier providing the gift info, there was mention of a gift_subscription_id. This id would either be the event id or a new field in the channel.subscription.gift event called gift_id. Ideally a new field should not be needed as the id should be the event itself, but it depends on the infrastructure packing this together. Also explained in https://twitch.uservoice.com/forums/310213-developers/suggestions/43813413-provide-a-gift-event-id-in-the-channel-subscribe

   channel.subscription.update | New Topic

   • New topic for subscription changes such as tiers or gift continuations who don't drop from a previous tenure. https://twitch.uservoice.com/forums/310213-developers/suggestions/42454273-subscriber-upgrades
     

   channel.subscription.progress | New Topic

   • New topic for subscription tenure metrics. This is mentioned in Barry's User Voice (link provided) which would be useful for metrics along side channel.subscription.begin and channel.subscription.end for users who don't share their resub in chat. https://twitch.uservoice.com/forums/310213-developers/suggestions/42008110-please-provide-an-event-sub-that-emits-resub-paym

   channel.subscription.{all}

   • Transaction method to allow understanding how a sub was acquired and react appropriately. In the past Prime was utilized as a tier of sub in places such as PubSub, but this has been pointed out to not necessarily be the case. is_prime is too rigid and ignores other acquisitions such as iOS tokens. Instead a data point of transcation_type may be more idealistic. https://twitch.uservoice.com/forums/310213-developers/suggestions/42012043-add-is-prime-to-subscription-events

   ---

   Relevant User Voice Topics

   • https://twitch.uservoice.com/forums/310213-developers/suggestions/43813413-provide-a-gift-event-id-in-the-channel-subscribe
   • https://twitch.uservoice.com/forums/310213-developers/suggestions/43241439-channel-subscriptions-to-include-who-gave-the-gift
   • https://twitch.uservoice.com/forums/310213-developers/suggestions/42454273-subscriber-upgrades
   • https://twitch.uservoice.com/forums/310213-developers/suggestions/42008110-please-provide-an-event-sub-that-emits-resub-paym
   • https://twitch.uservoice.com/forums/310213-developers/suggestions/42012043-add-is-prime-to-subscription-events

   Request

   Organize channel.subscription topics to allow for alert like notifications to properly be provided. What displays in chat should be able to be mimicked via EventSub topics without having active tracking or additional api calls; Provide missing data where needed; Create new topics to fill in the gaps.

   ---

   Current Scenarios

   Brand New Subscriber: If a user subscribes for the first time in the channel, we get an alert as soon as they sub. This is incidental that it works properly for stream based alerts, as we are actually receiving the payment transaction rather than the in chat event.

   Prime Gaming… more

   74 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  ·  EventSub  ·  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. Pinned messages API

   Please provide an API to

   • pin existing message
   • pin a new message
   • unpin a message

   Which should work using a moderators token in line with the announced new feature

   72 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

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

   We're planning to add support for pinned messages in the API and EventSub.

6. Allow Developers to Rollback to Approved Extension Versions

   Allowing developers to roll back a released version to another (approved) version would allow developers to quickly address breaking issues without going through a review process.

   72 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

   Long-Term Consideration  ·  3 comments  ·  Extensions  ·  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. Please provide an event sub that emits "resub payments"

   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

   69 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

   12 comments  ·  EventSub  ·  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
   Long-Term Consideration  ·  AdminJon Bulava (Developer Advocate Lead, Twitch) responded

   Changing status to long-term. To preserve ecressey's previous comment, "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."

8. Add "channel follows" as a topic in PubSub

   Add a new topic in the PubSub API for new channel followers event, with the same behavior of the "Channel Subscriptions" topic.

   68 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

   5 comments  ·  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. 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

   66 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

   We are investigating this for EventSub.

10. restrictions to prevent bot follows

    The idea is simple: Add the same phone & email verification options to the ability to actually follow a channel, and thus also giving account age requirements to be able to follow a channel. This will allow small streamers being targeted by hate raid Bot attacks to simply prevent the bot attacks easily, instead of being driven off the platform.

    65 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

    8 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

11. Expose Founders in the API
    65 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

12. Raid Now

    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.

    53 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

    Long-Term Consideration  ·  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

13. Extend API to be able to Ban/Unban up to 100 ID's similar to blocking

    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

    52 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

14. API to CRUD the new "Profile Block"

    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

    52 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

    6 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. Vod chat for helix

    Currently twitch embed does not support vod chat and neither does the helix api.

    Twitch only allows vod chat to be seen directly on the website.

    This data could be used in a great number of ways by third-parties particularly video editors.

    Please add a way to retrieve chat for vods

    No? ok. Sadge

    51 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

    6 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

16. Moderator Actions PubSub topic should work for all moderators of the channel

    The chat_moderator_actions topic in the PubSub documentation appears to only work with a broadcaster OAuth token. This prevents third-party modding tools that don't use some kind of centralized system from accessing information that is vital for effective modding (such as which mod performed an action, actions that aren't otherwise visible like unbans and viewing and approving messages filtered by AutoMod).

    With a centralized system the broadcaster could provide a token somehow that the moderators don't need to have access to directly, however with purely clientside tools this is not feasible. I'm also not sure why moderators should not have access to that kind of information.

    The moderator actions PubSub topic previously announced by Twitch Staff on the developer forums (https://discuss.dev.twitch.tv/t/in-line-broadcaster-chat-mod-logs/7281) does allow moderators to access this information. The announcement of the added "channel:moderate" scope requirement (https://discuss.dev.twitch.tv/t/upcoming-oauth-scope-requirements-for-pubsub/23203) gave me the impression that the old topic was now officially supported, so it's quite surprising and worrying that the topic added to the PubSub documentation has changed in a way that would break tools that many moderators have been using for years.

    It would be very helpful to either add/clarify the old topic as officially supported as well, change the token requirements for the new topic or provide some other way to get the same information with a moderator's token.

    The chat_moderator_actions topic in the PubSub documentation appears to only work with a broadcaster OAuth token. This prevents third-party modding tools that don't use some kind of centralized system from accessing information that is vital for effective modding (such as which mod performed an action, actions that aren't otherwise visible like unbans and viewing and approving messages filtered by AutoMod).

    With a centralized system the broadcaster could provide a token somehow that the moderators don't need to have access to directly, however with purely clientside tools this is not feasible. I'm also not sure why moderators should not have access… more

    51 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

    3 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. Make embeds work on iOS web based apps (like ionic)

    While it works on Android, it is still impossible to use iframe embeds on web-based mobile iOS apps. The reason being that iOS' WKWebView expects <schema>://<host> in the CORS headers returned by Twitch. Twitch uses the parent parameter to generate those headers. Unfortunately, iOS prevents the use of http://, https:// and file:// as schemas and forces us to use a custom schema like ionic://localhost (or anything else) for accessing local files.

    The request is to add the ability for twitch embeds to return a CORS header that can match a custom scheme like ionic://localhost.

    I read through all forum topics on that subject but none provides a working solution. Please see the following discussions for an in-depth explanation why the current state of twitch embed cannot work and a suggestion for a solution:

    • https://discuss.dev.twitch.tv/t/embedded-player-within-ios-web-based-mobile-app-e-g-ionic-not-working/36227
    • https://stackoverflow.com/questions/68105361/twitch-embedded-player-on-ionic-ios-not-working

    While it works on Android, it is still impossible to use iframe embeds on web-based mobile iOS apps. The reason being that iOS' WKWebView expects <schema>://<host> in the CORS headers returned by Twitch. Twitch uses the parent parameter to generate those headers. Unfortunately, iOS prevents the use of http://, https:// and file:// as schemas and forces us to use a custom schema like ionic://localhost (or anything else) for accessing local files.

    The request is to add the ability for twitch embeds to return a CORS header that can match a custom scheme like ionic://localhost.

    I read through all… more

    46 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  ·  Embeds  ·  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. Allow getting realtime updates on polls/predictions/channel points redemptions through websockets for all users

    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 which is otherwise publicly available in chat. If you want me to separate the features into different posts I'd be happy to do it.

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

    46 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

    Under Consideration  ·  3 comments  ·  EventSub  ·  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. 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

    46 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. Provide Soundtrack Control API

    Provide an API for third parties to control soundtrack

    Including but not limited to

    • Play/Pause
    • Volume control
    • Playlist entries in "now playing"
    • Current song that is playing
    • Play head position in the current song
    • playlist play head position
    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

    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