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

171 results found

  1. There are reference to V5 API here to get user and channel ID.
    Combined with the GitHub Sample at https://github.com/twitchdev/pubsub-javascript-sample that is still using it this is very confusing to get to work.
    Suggest to update the sample and this article to reference the helix APIs instead.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. It would be very easy to build and design for if there were official typing for all data endpoints. The data between all the different API's for the same data isn't consistent, and with event sub, since it no longer relies on the underlying Helix endpoint, that data can now be different too. This will also mitigate typos on the docs which causes huge headaches when trying to code for API responses and the data not working, or missing fields. The typing can specify which fields are required and which are optional, so when designing your app, you can easily…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. https://dev.twitch.tv/docs/irc/guide#command--message-limits says:
    - 20 authenticate attempts per 10 seconds per user (200 for verified bots)
    - 20 join attempts per 10 seconds per user (2000 for verified bots)

    however it's unclear how these limits apply to anonymous connections. Is there no limit to join attempts at all when you have authenticated as an anonymous user? And do authentication attempts for anonymous users (NICK justinfan12345) count towards the rate limit?

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. It should be more obvious that Twitch IRC: Commands needs the commands capability, Twitch IRC: Tags needs the tags capability, Membership page needs the membership capability.

    IE:

    Literally add a paragraph at the top to the effect of

    The Twitch IRC responses outlined on this page requires the connection to have requested the $whatever capability as outlined on the https://dev.twitch.tv/docs/irc/guide#twitch-irc-capabilities Capabilities section of the guide.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. https://dev.twitch.tv/docs/irc/tags#usernotice-twitch-tags documents anonsubgift and anongiftpaidupgrade. I found this announcement post https://discuss.dev.twitch.tv/t/anonymous-sub-gifting-to-launch-11-15-launch-details/18683 saying that apparently it was temporarily disabled as a workaround. As far as I can tell to this day the workaround is used. The documentation should be updated to remove the originally planned but never put into service types, and instead document that anonymous gifts come from AnAnonymousGifter.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The examples for Google Analytics suggest using jQuery. Which is extra bloat if an extension hasn't use jQuery to start with and can lead to confusion

    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

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

    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)
  8. Extensions Manager Overview -> Capabilities -> Request Identity Link

    Description refers to viewer as a male ('his'). This is likely to offend some people?

    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)
  9. 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
    }

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

    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)
  11. 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"

    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. Missing documentation for channel:send:events scope.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Hello, thanks for this great page! But there is no info about "expiresin" field when using refresh token. Refresh request returns "expiresin" field too. Am I doing something wrong?

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Description of 'outcomes' in 'Create Prediction' says that array size must be 2. Isn't the current limit between 2 and 10?

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Since the docs are so long, and each header has an ID you can link to, you should put a link icon that copies the link to clipboard for each header for easy sharing.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. This page suggests "OAuth Authorization code flow" but i don't believe this is correct because for a chatbot to be effective you would need the access token to never expire or the process to handle expiry and refresh to be event driven. Having a robot/non-existing user login seems misleading or wrong.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. This tutorial looks very unprofessional.

    The example GitHub repository is not available from an official Twitch source, but lives in someone's personal
    account at:
    https://github.com/sonia145

    These GitHub organizations would be better alternatives:
    https://github.com/twitchtv
    https://github.com/twitchdev

    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)
  18. Unhelpful page. I want to send an API request to test through Postman, but I do not understand what format to put it in. It is asking for an OAuth token, but that request does not mention anything about that. Very confusing.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. the V5 scope 'user_read' is not listed here. In the migration document it suggests that that is equivalent to the helix scope user:read:email. Is that correct?

    Is there a V5 scope that matches the new helix user:read:broadcast

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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

    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.

  • Don't see your idea?