Developers

  1. Add a Developer Tools Section to the Devsite

    The creator dashboard available to broadcasters has a section with Streaming Tools that helps them identify what third-party tools can support them to achieve a high-quality stream.

    The same experience should be available on the dev site so new developers can find which third-party tools they can leverage to build a top-notch Twitch integration.

    9 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Started  ·  1 comment  ·  Developer Site  ·  Flag idea as inappropriate…  ·  Admin →
  2. 2FA status in users endpoint (when authing as the user)

    We third party dev's often build tools that assist with moderation actions/services for broadcasters.

    We tell Moderators to enable 2FA, but we have no way to check it.

    It would be useful to block Logins to our tool if 2FA is not enabled. But 2FA data is not surfaced in the API and there's no way to require a User to be 2FA during the login/oAuth loop.

    I'd like to see the users endpoint(s) provide 2FA status.
    I expect this to be behind the user read or openID scopes.

    openID allows email verified. Why not 2fa status (for example)

    Worth…

    9 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  3. Expose id of the user who initiated the ban/timeout

    For /moderation/banned and /moderation/banned/events.

    4 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add subscriber only status to Streams API endpoint.

    Right now there is no official way (there is an undocumented endpoint) to determine whether a stream is sub only or not. Subscriber only status prohibits a lot of people from interacting with the stream, so it'd make sense for applications to be aware of such a state.

    4 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add functionality to query broadcaster id and user id for the Bits transaction API

    It would be convenient to have the ability to query Bits transactions based on broadcaster id and user id. This is extremely helpful for Extensions with lots of transactions and saves on calls to the API that would be necessary for paginating until the desired transaction is found.

    5 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  6. 2 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add subscription status to Viewer's JWT

    Add subscriptionStatus to extension JWT. Currently subscriptionStatus is in Twitch.ext.viewer. With it in the JWT, it can be verified by an extension backend.

    7 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add the bits:read scope to bits enabled extensions

    I'm looking to add functionality to an extension where all bits count but bits within the extension have a weighting against those that aren't. I have my own bits transactions through the transactions endpoint but at the moment I have to ask for the scope separately. As my extension is already asking for the `channel:read:subscriptions` I thought it may be a good option to add this as an extra scope to ask for or possibly ask for within the same auth loop as the subscription read

    3 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  9. 4 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add created timestamp to /helix/users

    A user's created timestamp is not yet available through Helix. The updated timestamp is personally less useful but would be nice for consideration.

    4 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Subs Tenure in Helix

    We would like subs tenure in Helix in order to use this for merch extensions providing tenure-based merch options.

    5 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  12. Mature flag on Get Streams endpoint

    Get Streams does not denote if the stream is mature or not.

    2 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  13. Include username in onAuth callback when a user has granted ID access.

    Some third-party developers request id access on their Extensions just for the purpose of getting a viewer's username to build a more personalized experience. The only way to do so is by relying on the Helix user endpoint on their EBS. The Helix team already modified any payload that has a user id to also deliver a username and save developers the extra step of using the /users endpoint, so it's natural for Extensions to follow that path.

    3 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Extensions  ·  Flag idea as inappropriate…  ·  Admin →
  14. 5 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  15. Verified Developer Badge

    Partners get a verified badge, it would be nice for published developers to get a badge too, maybe after a certain usage requirement of their extension, like how partners have to hit certain limits to become partner, maybe enough usages or page views of the extension will get a dev a badge.

    4 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Developer Site  ·  Flag idea as inappropriate…  ·  Admin →
  16. 2 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  17. 2 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  18. 2 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  19. 2 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
  20. 2 votes
    Sign in Sign in with OpenID Connect
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base