Skip to content
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

105 results found

  1. I guess I have found a bug in the Twitch EventSub documentation, the actual sort order of event attributes doesn't seem to be the way they are documented.

    The last two attributes of the Channel Points Custom Reward Redemption Add Event (https://dev.twitch.tv/docs/eventsub/eventsub-reference#events) are according to the documentation reward and redeemet_at whereas the API returns it as redeemet_at and reward. Either way the documentation is wrong or the API is wrong.

    It would be great for further development with the EventSub if this could be fixed.

    Thanks a lot and kind regards
    Moritz from dialogikTV

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    Deferred  ·  2 comments  ·  EventSub  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Scope formatting inconsistency. The channel.chat.usermessagehold and channel.chat.usermessageupdate sections have the word "scope" inside the code tag instead of outside like the other sections.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. EventSub recently got a few new chat-related subscription topics, most notably receiving chat messages, as described here: https://discuss.dev.twitch.com/t/available-today-twitch-chat-on-eventsub-an-api-for-sending-chat-and-the-conduit-transport-method-for-eventsub.
    Our chat bot, and I imagine other peoples' bots might as well, is reacting to incoming whispers. To be able to migrate off of IRC it would be necessary to also add a new subscription topic for receiving whispers.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. It would be nice to be able to have bots/alerts respond to when viewers follow a streamer shouted out on the channel they're being shouted out from.

    Often when getting a raid and shouting out the raider I can't tell if anyone actually follows through with following the person who raided.

    The ability to provide an alert, or chat message thanking those who click the follow button could improve the engagement on shout outs. Or at the very least provide insight to the streamer if they're being effective at promoting others.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. I think it would be useful to add the possibility to select in which shard in a conduit a subscription will be created. This would made the developer to have more control over subscriptions created in a conduit. I think this feature would fit in as an optional parameter in the request body at creating a subscription within a conduit.

    I know the conduits are made to balance the traffic over shards and connections but giving the developer more controll over which subscriptions goes in which shards is something that will make developing over conduits better.

    In my opinion this…

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. as a streamer, I want to be able to subscribe to Guest Star events that involve my user id as a guest; currently, I can only subscribe to events using the host channel's ID as the condition.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Without code samples/examples, I find the documentation minimally useful. I've got a clientid, clientsecret, appid, appsecret, token? Bearer token, eventsuburl, callbackurl, etc. While I appreciate you listing what RESPONSE might look like, it would be nice to see at least a basic "hello world" code sample. For example, since minimal auth (none?) is needed to subscribe for when a streamer goes live, it seems that would make a nice example of the overall flow.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. While the API doesn't support channel point goals at all right now, I think it would be beneficial for developers to have ways to read the progress of channel point goals, for example for displaying the progress on overlays or having events triggered when it finishes.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. excuse,why i can not received message what other viewer send in the chatroom,but only received message what my bot send ,such as "@badge-info=;badges=;color=;display-name=yesankin;emote-sets=0,300374282;id=7fcf74eb-46ad-41ef-b04e-8aeac3cbab20;mod=0;subscriber=0;user-type= :tmi.twitch.tv USERSTATE #kathyvv"

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add a broadcaster ID to the https://dev.twitch.tv/docs/api/reference#delete-eventsub-subscription endpoint so we can do a simple API call when we get a user authorization revoke to be able to clean up all eventsub subscriptions for that broadcaster.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. PubSub provides withheld messages, approves and rejects through their API. Ingesting this data through EventSub would be great too!

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. It would be extremely useful to tie a raid back to a stream ID.

    The event includes broadcaster IDs and logins, but not which stream is being raided FROM and TO.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. You need to explain better the verify signature and also give examples in some languages, not in pseudocode, I am still unable to verify my signatures with Java, I am blind here, I am guessing what do you mean by "raw bytes of the request body" specially the "raw bytes" part.

    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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?