90 results found

1. Clips EventSub subscription type (retitled)

   Please provide a Webhook topic for when a Clip is created, edited or deleted

   Also provide a notification for when a Clip reaches certain view milestones.

   320 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

   13 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

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

   77 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

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

   70 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 Relations, 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."

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

   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

   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

5. channel subscriptions to include who gave the gift if it's a gift

   Extend EventSub subscriptions topic to include information about who gave the gift if it was a gift subscription.

   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

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

   We are planning a few updates to subscription payloads, including this item.

6. Add is_prime to subscription events

   Add a flag, which is true, when a subscription is made through Prime Gaming. Distinguishing between a regular sub and a Prime sub allows us to react differently on these cases, like also being able to promote the free Prime Gaming sub.

   39 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  ·  2 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

7. On EventSub create if 409 return ID of the conflicting Subscription

   Extend

   {
   "error": "Conflict",
   "status": 409,
   "message": "subscription already exists"
   }

   to

   {
   "error": "Conflict",
   "status": 409,
   "message": "subscription already exists",
   "id": "id of the eventsub subscription that conflicts"
   }

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

8. Please provide an eventsub around advert/commercial informationm

   A number of streamers have re signed with Twitch with new Contracts.
   Those new contracts often include a requirement to run adverts

   A request for tooling general occurs from the Streamer to a developer for tools relating to running commericals

   Please provide eventsub topics that provide the following information

   • An advert started, including
     • which user/editor started those ads
     • duration of those ads
     • did it do picture in picture or full screen (if possible and if it's the same for everyone whom saw an ad)
     • how long prerolls are disabled for
   • An advert completed it's duration
   • Adverts are cleared to run again (theres no status endpoint to get this information, see other UV's)

   A number of streamers have re signed with Twitch with new Contracts.
   Those new contracts often include a requirement to run adverts

   A request for tooling general occurs from the Streamer to a developer for tools relating to running commericals

   Please provide eventsub topics that provide the following information

   • An advert started, including
     • which user/editor started those ads
     • duration of those ads
     • did it do picture in picture or full screen (if possible and if it's the same for everyone whom saw an ad)
     • how long prerolls are disabled for
   • An advert completed it's duration
   • Adverts are cleared to run… more
   31 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  ·  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

9. Provide Cheermote and Emotes information for EventSub Cheer Events

   When viewers cheer, they use cheermotes and commonly emotes in their cheer messages. Unfortunately, the payload received from EventSub's channel.cheer callbacks only have the raw text as entered by the user, with no indiciation of which portions of that text are cheermotes nor emotes. Thus, I propose the following update to the callback payload, similar to the channel.subscription.message event, that passes along the data for both so that a consumer of EventSub can reconstruct the message:

   {
       "subscription": {
           ...
       },
       "event": {
           ...
           "message": {
               "text": "Rah Rah Cheer! cheerwhal1 Cheer100 notACheer101 finite6ThrowBall",
               "cheermotes": [
                   {
                       "begin": 16,
                       "end": 26,
                       "prefix": "cheerwhal"
                       "id": "1"
                   },
                   {
                       "begin": 27,
                       "end": 34,
                       "prefix": "Cheer"
                       "id": "100"
                   }
               ],
               "emotes": [
                   {
                       "begin": 48,
                       "end": 64,
                       "id": "emotesv2_4133039724974aa59589549eae677d03"
                   }
               ]
           },
           ...
       }
   }
   

   When viewers cheer, they use cheermotes and commonly emotes in their cheer messages. Unfortunately, the payload received from EventSub's channel.cheer callbacks only have the raw text as entered by the user, with no indiciation of which portions of that text are cheermotes nor emotes. Thus, I propose the following update to the callback payload, similar to the channel.subscription.message event, that passes along the data for both so that a consumer of EventSub can reconstruct the message:

   {
       "subscription": {
           ...
       },
       "event": {
           ...
           "message": {
               "text": "Rah Rah Cheer! cheerwhal1 Cheer100 notACheer101 finite6ThrowBall",
               "cheermotes": [
                   {
                       "begin": 16,
                       "end":

   … more
   29 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  ·  2 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

10. Provide emote information for EventSub Channel Point Redemption Events

    Emotes are a commonly used feature of Channel Point Redemptions requiring messages. Unlike the EventSub Subscription Message events which provide emote ID and placement data, Channel Point Redemption events do not. I propose the following change to the Point Redemption notification payload:

    channel.channel_points_custom_reward_redemption.add and channel.channel_points_custom_reward_redemption.update:

    {
        "subscription": {
            ...
        },
        "event": {
            ...
            "user_input": {
                "text": "Channel Point Message! finite6ThrowBall",
                "emotes": [
                    {
                        "begin": 24,
                        "end": 40,
                        "id": "emotesv2_4133039724974aa59589549eae677d03"
                    }
                ]
            },
            ...
        }
    }
    

    This allows for a client to properly construct the channel point redemption input, with emote images, similar to the channel.subscription.message event.

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

11. Please provide an eventsub for pinned messages add/removal

    Provide a topic for when the pinned message changes/added/removed from a channel

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

    We plan to support pinned messages in the Twitch API and EventSub.

12. EventSub Subscription Type: Advertisement Started

    I think an EventSub subscription type that would be really useful is one that alerts when an advertisement begins from the user's scheduled Ad Manager. This would allow bots the ability to post a message to users about the ad and remind them about subscribing and such when the ad begins.

    19 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

13. Add Stream ID to stream.offline

    Premise: stream.online encodes an id of the stream. stream.offline does not have such an id. Being able to pair this specific id with an online and offline state would be beneficial.

    Objective: Add the matching id to stream.offline that pairs with stream.online

    Notes: While it could be argued that a single broadcaster can only be live with a single id, it is still data oriented wise, more beneficial to have a symmetrical up and down payload, allowing quick queries on a state of a stream. Imagine a scenario where an online and offline event fire roughly at the same time. This creates a race condition that should not happen, but in theory still could at the current state.

    Premise: stream.online encodes an id of the stream. stream.offline does not have such an id. Being able to pair this specific id with an online and offline state would be beneficial.

    Objective: Add the matching id to stream.offline that pairs with stream.online

    Notes: While it could be argued that a single broadcaster can only be live with a single id, it is still data oriented wise, more beneficial to have a symmetrical up and down payload, allowing quick queries on a state of a stream. Imagine a scenario where an online and offline event fire roughly at the same time.… more

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

14. Please provide a topic(s) for all kinds of moderator actions

    We have bans/timeouts on the bans topic.

    We don't have a feed for message deletions.
    Or whom triggered a raid
    Or whom triggered a host.

    Some channels have a need to track/log all moderator actions for later reconcilliation, not just bans.

    (Or tracking down a rogue mod doing hosts when they shouldn't for example)

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

15. Also provide in channel.cheer an array of bits used

    Summary:
    A cheer message can be multiple cheers in a single payload. Providing the individual cheer components in an int array would provide data that is not currently there. Emote placement, while also desired, would be still more work than should be necessary at first glance to determine the bits used.

    Example: **
    BarryCarlyon PogChamp100 PogChamp100 Party100 Wow Soaryn is Frustrated!
    This would result in **"bits": 300; however this is incomplete and would be desired to also have something like "bits_used": [100,100,100]

    Reasoning:
    While again, emote placement would help, determining the bits used from it would be extra and redundant computational work that was already processed on Twitch's side. On the same note, determining in the emote where the cheer values actually start vs the emote regex may cause issues for this particular use case, unless on the client side a running emote store was kept.

    Related Event(s):
    - channel.cheer

    Summary:
    A cheer message can be multiple cheers in a single payload. Providing the individual cheer components in an int array would provide data that is not currently there. Emote placement, while also desired, would be still more work than should be necessary at first glance to determine the bits used.

    Example: **
    BarryCarlyon PogChamp100 PogChamp100 Party100 Wow Soaryn is Frustrated!
    This would result in **"bits": 300; however this is incomplete and would be desired to also have something like "bits_used": [100,100,100]

    Reasoning:
    While again, emote placement would help, determining the bits used from it would be extra and redundant… more

    15 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  ·  2 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

16. Channel/Global Emotes have changed

    A topic to account for emotes being added or remove from "global" or a specific ChannelID would be useful.

    It's hamstrung by

    https://twitch.uservoice.com/forums/310213-developers/suggestions/39547780-emotes-by-channelid

    As we can't catch up

    There are a number of Twitch Extensions that would be good to know if/when emotes change. (HypeMeter for example)

    And Developers of single channel bots will need to know so they can add/remove emotes from any channel commands.

    It's also useful for custom channel tooling to keep lists up to date in custom tooling if/when https://twitch.uservoice.com/forums/310213-developers/suggestions/41137957-upload-emotes is actioned as well

    This includes but is not limited to

    • regular subscriber emotes
    • bits/cheer emotes
    • the channel sub badges
    • the channel bits badges
    • any other channel specific imagery that may be utilised in chat

    A topic to account for emotes being added or remove from "global" or a specific ChannelID would be useful.

    It's hamstrung by

    https://twitch.uservoice.com/forums/310213-developers/suggestions/39547780-emotes-by-channelid

    As we can't catch up

    There are a number of Twitch Extensions that would be good to know if/when emotes change. (HypeMeter for example)

    And Developers of single channel bots will need to know so they can add/remove emotes from any channel commands.

    It's also useful for custom channel tooling to keep lists up to date in custom tooling if/when https://twitch.uservoice.com/forums/310213-developers/suggestions/41137957-upload-emotes is actioned as well

    This includes but is not limited to

    • regular subscriber emotes
    • bits/cheer emotes
    • … more
    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  ·  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

17. Subscriber upgrades

    IRC has a number of "upgrade" events

    giftpaidupgrade / anongiftpaidupgrade and one related to "prime to real" that I don't have the tag/msg-id for

    A "subscriber upgrades" topic would be useful, if this doesn't fall under "sub notifications" - https://twitch.uservoice.com/forums/310213-developers/suggestions/42008104-please-provide-an-event-sub-that-emits-sub-notifi

    I could see a benifit to having this as a seperate topic, or tied into the "notifications" topic

    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

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

    We are investigating adding an EventSub subscription type for sub upgrade events.

18. Include Tags on channel.update

    This would allow things to happen if only a certain tag is set.
    That of course would require channel.update to fire for tags being edited as well

    Example: If a streamer wants to have an automated tweet sent out when they start a Giveaway, they could add the tag "Giveaway", which triggers channel.update and then the receiver can process and send a tweet on their behalf.

    13 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

19. Extend Get EventSub Subscriptions to lookup a single Sub by ID

    Extend

    https://dev.twitch.tv/docs/api/reference#get-eventsub-subscriptions

    To add a optional query string param of id to allow developers to lookup a single subscription.

    If a developer stores the ID's when the subs are created, they may want to spot check a single ID's status, or check the settings of it, without having to paginate or manually filter the results returned when using on of the currently offered filter options

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

20. Copy Hype train Begin/Progress/End for outbound raids

    Add three topics

    • Raid Begin, a channel started a /raid
    • Raid progress, the number of users in the raid changed (sensibly capped so not too spammy on the webhook, but if socket, more spammy perhaps)
    • Raid End, raid completed or was cancelled.
    13 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  ·  1 comment  ·  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