Skip to content
Translate Ideas and Comments
Choose language:
There was an error during translation

Developers

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

10 results found

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

    69 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  EventSub  ·  Admin →
  2. Trigger: Triggers whenever a broadcaster hosts on a broadcaster's channel.

    Motivation: To my knowledge it is not possible to query hosts in real time. In our Twitch Alerts Extension it is currently not possible to show when a streamer is hosted by another streamer.

    57 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  8 comments  ·  EventSub  ·  Admin →
  3. Please provide an eventsub topic for HypeChat so third parties can build Custom Overlay integrations and tie the information into other systems a channel may have including but not limited to custom analyitics or credit rolls and so on

    49 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  EventSub  ·  Admin →
  4. Currently EventSub allows subscriptions for Subscriptions, Gifted Subscriptions, Raids, Follows, and Cheers - All things that streamers like getting alerts for and calling out. However, it appears to be missing the ability to subscribe to being Hosted, another even that streamers thank their viewers for.

    I know that in theory, Hosts are handled by Notice messages, but as they are only sent to the broadcaster, chat bots are unable to act on the alerts. Obviously the data is available somewhere, since all the major bot services can trigger alerts, but for those of us that are trying to make our…

    43 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  1 comment  ·  EventSub  ·  Admin →
  5. Since HypeChats count towards HypeTrains.

    Both the EventSub and API offerings for HypeTrains need to be revised to include this new information

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
  6. channel.shoutout.create currently requires a moderator/broadcaster token.

    This defeats the point of a shoutout; channels do shoutouts exactly because they want other people to notice them. Restricting this subscription type prevents third-party chat applications from informing non-mods that a shoutout has taken place (thus defeating the point of the shoutout)

    Please remove the moderator scope requirement on channel.shoutout.create

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  3 comments  ·  EventSub  ·  Admin →
  7. Recently twitch removed notifications for smaller hosts. This is not ok. We want this back. We as a community need to band together to get this change reverted.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
  8. While creating a wrapper, I found the varying conditions for "user_id" to be frustrating and have resorted to creating a Map for subscription.type -> *_user_id condition. (broadcaster_user_id, from_user_id)

    I think it would be easier to always have the condition be "user_id" for a user, and then allow a second property for modifying the scope of the condition. So in the instance of "users.follow", it might look like:

    condition: {
        user_id: "1337"
        follow_source: "from"
    }
    

    What are your thoughts on this?

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  2 comments  ·  EventSub  ·  Admin →
  9. Currently, you can't tell if someone has gifted tier 1, 2, or 3 subscriptions. It could be a tier 3 subscription or 3 tier 1 subscriptions. Therefore, the information should be added.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  EventSub  ·  Admin →
  10. After a webhook fires, I'm given context to the UserID and Username. In the instance of "stream.online", I would like more information. In the old webhooks, I was given the full stream data object. Will there be a standard way of accessing the full data object of whatever is "notifying" the webhook? Or is it on me to use the existing Helix API to then get that information(user info, game info, broadcast info)?

    One thought would be to simply give the appropriate URL to POST to for more information, similar to how some APIs give a paginated cursor URL to…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Declined  ·  2 comments  ·  EventSub  ·  Admin →
  • Don't see your idea?