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

84 results found

  1. From: https://github.com/twitchdev/issues/issues/40

    Brief description

    https://dev.twitch.tv/docs/extensions/building/#using-the-configuration-service

    Mentions "twitch api reference" but the config service endpoints are on in the Extension Reference

    For extension examples that leverage the configuration service see the new Twitch API Reference. Also, see these repositories:

    Expected documentation

    Links to https://dev.twitch.tv/docs/api/reference but the configuration API is documented https://dev.twitch.tv/docs/extensions/reference#set-extension-required-configuration

    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

    Completed  ·  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)
  2. From: https://github.com/twitchdev/issues/issues/31

    Brief description

    The documentation doesn't advise anything regarding what languages/localses exist/are valid to be called.

    For example

    https://dev.twitch.tv/docs/api/reference#get-streams

    has a language query string argument, but doesn't advise what is valid for a langauge.

    Expected documentation

    Document the list of locales of if it matches a ISO, update documentation on endpoints using language/locale with a note about what is valid

    Additional context or questions

    Raised/queried on discord

    https://discordapp.com/channels/504015559252377601/523675960797691915/664243349309620225

    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

    Completed  ·  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)
  3. 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

    Completed  ·  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)
  4. Channel Update Notification Example states both user_id and user_name are returned, when actually it returns broadcaster_user_id and broadcaster_user_name

    Ref: https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types#channelupdate

    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

    Completed  ·  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)
  5. The documentation mentions "a unique ID" that is included with each notification, but doesn't mention the header name.

    The page should add documentation for the "Twitch-Notification-Id" header.

    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

    Completed  ·  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)
  6. The Documentation for the Get Broadcaster Subscriptions Endpoint has a description of Get all of a broadcaster’s subscriptions. - This is ambiguous and sounds like it returns the Subscriptions to other channels a Broadcaster has whereas it returns the users that subscribed to the broadcaster.

    I would suggest changing the description to say Get all of a broadcaster’s subscribers. instead.

    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

    Completed  ·  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)
  7. https://dev.twitch.tv/docs/authentication/getting-tokens-oauth

    Both Implicit code flow and authorization code flow label the first step as a "HTTP GET" instead of "this is a link that you need to put on a page for the user you wish to authenticate" or "you need to redirect the user to this page"

    Too many people are trying to curl/fetch the URL as the docs seem to label it as a HTTP GET request

    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

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

    Completed  ·  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)
  9. Hello,

    Searching in the documentation of the new API I have found these four small errors. They are not at all severe, but they should be remedied in order to facilitate the use of the API.

    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

    Completed  ·  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. https://dev.twitch.tv/docs/api/reference#get-users

    user:read:email disappeared and user:edit:broadcast now has the email scope's description.

    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)
  11. Similar to

    https://twitch.uservoice.com/forums/310213-developers/suggestions/39847792-pubsub-docs-don-t-mention-token-type

    All documentation should be revised to describe which kind of token and depending on token type what scopes are needed to call each endpoint.

    The documentation for the most part only mentions a scope and doesn't describe what kind of token to use

    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

    Completed  ·  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 scopes page on Authentication(https://dev.twitch.tv/docs/authentication/#scopes)

    is missing the documented scope from the Helix Get Moderators

    Returns all moderators in a channel.

    Authorization
    Requires OAuth Scope: moderation:read

    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

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

    Completed  ·  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. The linked status page does not exist and redirects to: https://www.atlassian.com/software/statuspage

    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

    Completed  ·  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. link that should show more info about broadcasting technical aspects, https://stream.twitch.tv/ leads nowhere

    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

    Completed  ·  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. This page should mention that "v5" and the "kraken" api refer to the same thing. Me and my friends always used "Kraken" to refer to this api, it's in the endpoint its self.

    I'm sure we are not alone in this, please mention that v5 IS the Kraken endpoint, you should even rename the side-section to say "Legacy Twitch API v5 (Kraken)"

    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

    Completed  ·  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)
  17. You changed the EventSub documentation between last night (Nov 16, 2021) and today (Nov 17, 2021). The new documentation is very confusing. Specifically speaking:

    • The Subscription Types documentation links on the left side are out of order and like-kind events are not next to each other. For example, "Redemption Status Update" should be next to "Channel Points redeem reward".
    • The Subscription Types are poor named, and it's a little difficult to figure out which Subscription Type goes to which event.
    • The URL to go straight to the section in the Subscription Types is different from the type supplied in an…
    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

    Completed  ·  2 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. There's a typo under mobile guidelines:
    "dimensionn"

    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

    Completed  ·  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)
  19. 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

    Completed  ·  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. Scope list says it's comprehensive, but it does not include user:read:email which is listed in some other docs.

    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

    Completed  ·  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)
  • Don't see your idea?