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

35 results found

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

    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

    3 comments  ·  API  ·  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. Extend EventSub subscriptions topic to include information about who gave the gift if it was a gift subscription.

    30 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

    6 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. Provide a topic for when the pinned message changes/added/removed from a channel

    18 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)
  4. From: https://github.com/twitchdev/issues/issues/25

    Brief description

    https://dev.twitch.tv/docs/pubsub#topics

    PubSub documentation mentions the requirement to use an oAuth token, but doesn't directly specify which type of token, nor the requirement for the UserID of the token to match the UserID of the topic.

    Authentication
    All topics require an OAuth token, but only some topics have a specific required scope (noted in the table below).
    
    Available Topics
    All topics require an OAuth token, but only some topics have a specific required scope (noted in the table).
    

    Expected documentation

    Authentication
    All topics require a User Access OAuth token, where the UserID of the token matches the
    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

    Planned  ·  1 comment  ·  Documentation  ·  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. Would be helpful to provide a openapi/swagger document or json schema for the objects here

    7 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

    Planned  ·  0 comments  ·  API  ·  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. Chat has a number of states, slow mode/follower only mode.

    Some moderationg applications involved monitoring for these states and responding as needed, and these applications will currently use PubSub but only in a logging capacity so alternatively connecting to chat for this data is perhaps overkill.

    Please provide an eventsub topic that relays
    - when/what Roomstate changes (slow on/slow off sub on sub off emote only)
    - which moderator/user triggered the change.

    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

    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. https://dev.twitch.tv/docs/irc#overview

    Row:
    client.connect();

    Should be replaced with:
    client.connect().catch((err) => {console.log('Connection error!', err)});
    or smth like that.

    Let's show users how to write good code, and show them, that all Promises should be handled. Unhandled promise rejections is bad!

    Tmi.js Library also have connect example which contain promise handling

    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

    Planned  ·  0 comments  ·  Documentation  ·  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. https://dev.twitch.tv/docs/pubsub

    Has no examples or documentation for payloads for chatmoderatoractions

    5 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

    Planned  ·  0 comments  ·  Documentation  ·  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. So it seems that when a user is banned or timed out, extensions unload/are unavailable to those users.

    This is not documented.

    It should be documented somewhere

    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

    Planned  ·  0 comments  ·  Documentation  ·  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. You provide information on how to remove a token, how to refresh a token, and how to define scopes for tokens, but you don't actually have any information on how to request a token, nor any sample code on that or applying token scopes. Given that this step is fundamental to any interaction with the Twitch API, this seems like a fairly major omission.

    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

    Planned  ·  2 comments  ·  API  ·  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. 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

    Planned  ·  0 comments  ·  Documentation  ·  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. The graphs on this page don't look right. The graph syntax is displaying, not the graph itself.

    %% Extensions Overview Diagram
    graph LR
        Twitch --> | - postMessage - | Extension
        Extension --> | - postMessage - | Twitch
        Extension --> | - HTTP - | APIs
        Extension --> | - HTTP - | EBS[Extension Backend]
        Identity --> Twitch
        Chat --> Twitch
        Memes --> Twitch
    
    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

    Planned  ·  0 comments  ·  Documentation  ·  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. As per this other uservoice

    https://twitch.uservoice.com/forums/310213-developers/suggestions/39645769-moderator-actions-pubsub-topic-should-work-for-all

    The moderation actions PubSub at time of writing requires a key from the channel you wish to listen to with the scope channel:moderate

    However the scopes page

    https://dev.twitch.tv/docs/authentication/#scopes

    is mis leading as it only talks about how the scope works for chat leading to confusion with pubsub operation

    "Perform moderation actions in a channel. The user requesting the scope must be a moderator in the channel."

    The wording needs to be changed and/or the pubsub topic adjusted to support being able to read moderator events as a moderator

    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

    Planned  ·  0 comments  ·  Documentation  ·  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. URL

    https://dev.twitch.tv/docs/authentication#validating-requests

    {
    "clientid": "<your client ID>",
    "login": "<authorized user login>",
    "scopes": [
    "<requested scopes>"
    ],
    "user
    id": "<authorized user ID>"
    }

    should be

    {
    "clientid": "<your client ID>",
    "login": "<authorized user login>",
    "scopes": [
    "<requested scopes>"
    ],
    "user
    id": "<authorized user ID>",
    "expires_in": timeInSeconds
    }

    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

    Planned  ·  0 comments  ·  Documentation  ·  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. From: https://github.com/twitchdev/issues/issues/69
    Brief description

    Some endpoints return a 204 code no content.
    But this is only highlighted in the example responses and not in the "main documentation"

    For example

    https://dev.twitch.tv/docs/extensions/reference#send-extension-pubsub-message
    https://dev.twitch.tv/docs/extensions/reference#send-extension-chat-message

    Each endpoint documented could be extended to include usual HTTP response codes.

    Expected documentation

    The expected response code for success when theres no body response
    Common non 2xx codes for the endpoints

    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

    Planned  ·  0 comments  ·  Documentation  ·  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. From: https://github.com/twitchdev/issues/issues/14

    Brief description

    https://dev.twitch.tv/docs/api/webhooks-reference

    the hub.topic section is out of date, in the JSON Body Parameters

    Expected documentation

    Just changed it to something like "refer to later in this docs for the available topics"

    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

    Planned  ·  0 comments  ·  Documentation  ·  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. Please add a JS Helper function

    Which is the equivalent of window.Twitch.ext.viewer.sessionToken but for the helixToken of window.Twitch.ext.viewer.helixToken.

    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

    Planned  ·  1 comment  ·  Extensions  ·  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. As the Helix API reference page (https://dev.twitch.tv/docs/api/reference) is continuing to grow it it is starting to become unwieldly with the number of entries.

    It would be beneficial to the docs to create sections for different areas of the API. Appropriate names for the sections are already listed in the API, as at the top of the reference page is a table that has a 'Resource' column which would be perfect for this usage, and that table can remain at the root reference page so that devs can see at a glance what endpoints are in what section, then…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Planned  ·  cycene responded

    This has been on the roadmap, and is planned for early 2021.

  19. https://dev.twitch.tv/docs/api/reference#modify-channel-information

    The example calls uses JSON, but the documentation talks about Query String/URL encoded form.

    Docs should cover both possibilities and examples should cover both methods

    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

    Planned  ·  0 comments  ·  Documentation  ·  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. https://dev.twitch.tv/docs/embed/ and it's child pages mention the requirements for parent but never SSL

    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

    Planned  ·  0 comments  ·  Documentation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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