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

Developers

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. stream.online has started_at please add ended_at to stream.offline

    So stream duration can be determined as accurately as possible as needed./

    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  2. I have a epic idea would someone contact me at (404)734-2419
    Or my email ceoduosleev@gmail.com or you can Google me for more contact info ceoduosleev

    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  3. under subscription limit, amount of entries per page should be noted

    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Other than knowing someone is online, there is still a need to utilize the API for getting related information about a stream.

    It would be nice to have an all-in-one "here's everything about this stream going live" instead of requiring additional calls (especially if there's a possibility of caching delays).

    Something along the lines of the data provided for channel.update would be nice

    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  ·  Flag idea as inappropriate…  ·  Admin →
  5. Please provide an eventsub topic that notifies when the extensions active on a channel change.

    The payload should match what https://dev.twitch.tv/docs/api/reference#get-user-active-extensions outputs.

    For a broadcaster tool we generally wouldn't need to know what the change was. Just what the current config with.

    This would save two payloads (for an extension changing from panel 1 to panel 2)

    It would be useful to know what changed but less important.

    So add a "was_changed" boolean to the relevant record.

    So

        "component": {
          "1": {
            "active": true,
            "id": "lqnf3zxk0rv0g7gq92mtmnirjz2cjj",
            "version": "0.0.1",
            "name": "Dev Experience Test",
            "x": 0,
            "y": 0
          },
          "2": {
            "active":
    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  6. Today there is a ban event on the EventSub. It allows us to know who has been banned, by whom, and above all, if it is permanent or not, which allows us to make the difference in a ban and a timeout. This is not the case during the event of unban, we do not know if the origin, it was a permanent ban ...

    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  7. Everything is in the title. Today we do not know who created the prediction or the vote. It is necessary to make an API call, which is really sad ...

    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  8. No information how to unsubscribe from getting events to webhook

    1 vote

    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

    1 comment  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  9. Scenario:
    A viewer comes in and gifts 10 subs to the community; This fires off in theory 11 events. One event is the channel.subscribe.gift, while the other 10 are the individual channel.subscribe for the 10 users.

    Request:
    The channel.subscribe.gift has an id associated with its emission. Something that would benefit reactionary data would be each of the individual channel.subscribe events having a gift_event_id. If the sub was a gift, set the id to the channel.subscribe.gift event id.

    Use Cases:
    - A developer could choose to listen to the batched gift amount and react to that single event, then…

    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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":
    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

    Under Consideration  ·  2 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    8 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  ·  Flag idea as inappropriate…  ·  Admin →
  12. Step 2 is failing successfully with {"total":0,"data":[],"maxtotalcost":10000,"total_cost":0,"pagination":[]}. Why is this so ridiculously impossible to use? I've built API integrations with over 20 different web apps. This one is BY FAR the most difficult to use. All I'm trying to do is set up a webhook so that streamers can join my software and see when people subscribed.

    1 vote

    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

    2 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  13. https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#userauthorizationgrant

    Please extend user auth grant to include

    • all scopes shared between ClientID and userID
    • new scopes added to the relationshio when the auth occured

    Possible use cases include: auto determine from this eventsub, what other eventsub topics to auto create.

    4 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  ·  Flag idea as inappropriate…  ·  Admin →
  14. Please provide a topic(s) that emits events when

    • a segment "definition" (recurring or one off where supported) is updated created or destroyed
    • channel creates a vacation segment.

    It wouldn't notify when we get to monday/start of week and the schedule is "built"

    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

    1 comment  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  15. Limits like max length for transport.secret property would be good.

    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  16. The section title under the payload section of the extension.bits_transaction.create event is "Channel Hype Train End Notification Example" when it should read "Extension Bits Transaction Notification Example"

    1 vote

    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

    1 comment  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  17. Include the same data as received from https://api.twitch.tv/helix/moderation/banned/events. Primarily event timestamp (time when the ban/unban action occurred) and the id (allows checking for duplication with eventsub messages already received when pulling from helix)

    Add the following fields to "event" paylod for ban/unban eventsub messages:
    "id": "1IPFqmlu9W2q4mXXjULyM8zX0rb",
    "action_timestamp": "2019-03-13T15:55:19Z"

    1 vote

    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  ·  Flag idea as inappropriate…  ·  Admin →
  18. EventSub Beta for channel.prediction.end event/status should be consistent with helix casing of status, i.e "Valid values are RESOLVED, and CANCELED."

    1 vote

    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

    1 comment  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  19. EventSub Beta for channel.poll.end and channel.poll.progress event/status should be consistent with helix casing of status, i.e "Valid values are COMPLETED, ARCHIVED, and TERMINATED"

    1 vote

    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

    1 comment  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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…

    28 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

    Under Consideration  ·  2 comments  ·  EventSub  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?