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

202 results found

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

    Brief description

    Many API's don't document that they support first and after

    Expected documentation

    Document first/after in the optional query parameters

    Additional context or questions

    Missing First in Optional Query Parameters
    - Get Banned Users
    - Get Moderators
    - Get Moderator Events
    - Get Broadcaster Subscriptions
    - Get Videos

    Missing Pagination in the Return Values
    - Get Broadcaster Subscriptions
    - Get Videos

    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

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

    Mentions User OAuth and the optional scope, but doesn't mention that you can use an app access token for this endpoint to get "public" data.

    Authentication
    User OAuth Token
    Optional scope: user:read:email
    If this scope is provided, the response includes the user’s email address.
    

    Should probably read

    Authentication
    - App Access Token
    - User OAuth Token any/no scopes
    - User OAuth Token with scope: user:read:email response includes the user’s email address.
    
    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

    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)
  3. From: https://github.com/twitchdev/issues/issues/63

    Brief description
    The channel:read:redemptions scope is required by the Channel Points PubSub topic (https://dev.twitch.tv/docs/pubsub#topics) but not mentioned in the scopes overview (https://dev.twitch.tv/docs/authentication#scopes)

    Expected documentation
    The channel:read:redemptions listed on the overview page (https://dev.twitch.tv/docs/authentication#scopes)

    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

    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)
  4. Similar to https://twitch.uservoice.com/forums/310213/suggestions/38203978

    But include the date/time of when the ban record is for.

    So for example

    {
    "user_id": "SomeID",
    "user_login": "SOMElogin",
    "user_name": "SOMEdisplay",
    "expires_at": "",
    "reason": "",
    "moderator_id": "15185913",
    "moderator_login": "barrycarlyon",
    "moderator_name": "BarryCarlyon"
    }
    

    I have no idea when this ban happened.

    UseCase: For considering unbans when reviewing data in an external tool, the date/time of the ban will be considered to determine if the user who is banned has "served" their time or not

    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

    Completed  ·  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)
  5. Premise: Currently there is no way to identify a hype train from start to finish fully. Adding an id (Guid) would help alleviate tracking the train as it progresses as well as after it has finished.

    Expected: hypetrain_id be added to the begin, progress, and end payloads. Given a particular hypetrain, these events would have the same Id per hype train.

    Usecase: Being able to cache and query a hypetrain via id to infer if the train is still continuing. Using time, winds up as an oddity due to the elongation of time behavior when the goal is reached. This…

    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

    1 comment  ·  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)
  6. The bans topic will send an event for someone getting banned or timed'out from the channel.

    The bans topic doesn't tell you if it was a ban or a timeout.

    • Timeout's either need to be a seperate topic (not preferred)
    • The payload extended to include a time parameter, so timeouts can be differetiance (preferred)

    (Webhooks have the same problem ironically)

    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

    Completed  ·  2 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. Summary:
    In chat for the broadcaster and mods, when someone is banned the reason and responsible user is provided. Adding the user's identifiers and the message that was used when banning. Assuming there is a timeout equivalent planned or made this likely would need to be added there for consistency as well.

    Reasoning:
    This allows for up to date reasonings for why someone was banned without having to request this info separately.

    Related Topics:
    - channel.ban
    - channel.unban

    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

    Completed  ·  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)
  8. I added this to a comment on the existing idea request for a full CRUD set of API endpoints for the "Schedule" feature, but given that I believe a whole lot of use could be made of a "Read" endpoint for upcoming scheduled streams for a given channel, I thought it worthwhile to add this as a separate (and hopefully, much easier and quicker to implement) idea request.

    Please give this thorough consideration Twitch dev and product teams!

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

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

    Omits the description of "broadcastername" and as per https://github.com/twitchdev/issues/issues/3 it's the "dISpLaYNaME" of the caster not the username.

    So we have to do a second lookup to get the login for embed purposes

    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

    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)
  11. https://dev.twitch.tv/docs/api/reference#get-moderators Under optional parameter for user_id the description says for users who are banned in this channel for the moderators endpoint.

    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

    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)
  12. I would like to work with embeds, and more specifically a way to get how much the current player's stream latency is. From what I can tell, player.getPlaybackStats() was the only way to do this, and is now deprecated, and returns null 99.99% of the time. (I was lucky to get it working once, but yeah, it's gone.)

    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

    Completed  ·  3 comments  ·  Embeds  ·  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. Add a Webhook for Cheers

    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  ·  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)
  14. Messages held by AutoMod for review can be received through the documented chat_moderator_actions PubSub topic, however the New Twitch API does not appear to offer a way for moderators to approve/deny these messages, which would be useful for bots or moderators that use third-party tools to further customize their moderation experience.

    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

    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)
  15. Step 2 is unclear or wrong.

    I'm unable to make it work only by changing the Client-ID, nor removing the Authentication headers.
    You should precise that both need to be changed. Or maybe the OAuth token should work, but it doesn't.

    Fix your documentation it's important for developers that everything written here is clear and easily understandable by anyone (or at least devs).

    I recommend you to make a full review of the entire documentation... (Get some newbie devs to test it, if they do not understand, it's not written correctly)

    Also I really encourage you to make some sample…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. There are additional "cool down" options that are not reflected in the API

    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

    Completed  ·  1 comment  ·  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)
  17. The "GET /kraken/channels/<channel ID>/teams" endpoint is currently missing in the Helix API.

    I propose to either
    a) add the teams to the "GET /helix/channels" output, or to
    b) add new team endpoints to Helix altogether. (Teams need some love!)

    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

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

    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)
  19. The current Helix endpoint doesn't give the broadcast ID, so there's no way to grab which broadcast the VoD is from.

    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

    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)
  20. Target streamers: Coworking & costudying

    Use case: We've been using discord voice rooms or apps like studyverse to share people's cameras while focusing on their tasks, having an endpoint like this would allow a bot to automatically show affiliates/partners' camera, and mute subscribers as example.

    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

    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)

    This is possible with the Guest Star APIs in open beta now. If a guest is sharing audio/video, you can choose to disable those from coming through Guest Star.

  • Don't see your idea?