Developers

  1. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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. 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 →
  14. 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 →
  15. 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 →
  16. Give Broadcast ID for VoD Endpoint in Helix

    The current Helix endpoint doesn't give the broadcast ID, so there's no way to grab which broadcast the VoD is from.

    3 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. Ordering by date of helix endpoints

    Being able to order some of the Helix endpoints by date would be useful

    Follower for example would need in some cases 11k+ calls to the follower endpoint to just get the 100 followers who had followed for the longest time.

    This would also be good in the subscription endpoint if cumulative and streak get put into the Helix API

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

    Add a Webhook for Cheers

    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. /helix/moderation/enforcements/status - Return error messages instead of generic 500s

    When user IDs in the provided data payload do not exists, the endpoint returns a 500 error. Ideally this should return a more detailed error code with an error message related to user IDs.

    1 vote
    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 →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base