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

448 results found

  1. The existing Channel Emotes API response includes a 'bitstier' value of 'emote_type' for Cheer-earned emotes, but does not include any data about the actual number of bits required to earn the emote. Either the 'tier' attribute or a new integer-value (recommended) containing the number of bits for each emote would be very helpful. Adding the same attribute to the Emote Sets API response would also be useful and uniform.

    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)
  2. Creator Goals allow show streamer modification of the bar.

    Please expose the streamer selected modifications/preference in the API and EventSub payloads.

    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)
  3. I would like to request that the booleans phoneverified and emailverified be added to the Get Users API.

    email_verified was already a part of the v5 Get User endpoint.

    The reason for this is because I would like to create an app that uses the Twitch API that would only allow access to users that have a verified phone number, to prevent/reduce spam from malicious users.

    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

    2 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)
  4. Currently, there’s no way to separate between live streams and past broadcasts.

    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

    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)
  5. When I'm building an extension. I use a custom server to help simulate the Twitch Hosted test environment.

    To that end it would be useful for me to automatically fetch the new CSP fields from the API

    The Endpoint https://dev.twitch.tv/docs/api/reference#get-extensions Get Extensions currently provides a wealth of information about an Extension, including what things are available and enabled and which slots the extension can exist within.

    With the Dashboard deployment to allow entry of the new CSP fields. This endpoint should be updated to include the CSP data.

    Then I can auto collect the changes into my local test rig…

    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

    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)
  6. The Create Poll endpoint has optional query parameters to allow additional votes using either bits or channel points.

    However, it doesn't actually allow multiple votes. This can be seen in the pubsub response which explictly states that "multi_choice" (property indicating whether additional votes are allowed) is not enabled.

    When creating a poll through the web interface, it works just fine as it is created through the GQL and not the API. The GQL message also has an additional property to explicitly allow additional votes, on top of the properties that are used to either allow additional votes by bits and/or…

    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

    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)
  7. The TZIDs in https://dev.twitch.tv/docs/api/reference/#get-channel-icalendar are currently prefixed by a / so they are /America/New_York for example. Removing the leading slash should vastly improve compatibility with iCal parsers (since the timezones are essentially IANA timezones then).

    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

    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)
  8. The old semi-unofficial API endpoint to allow/deny messages held by AutoMod used to cause an event in the PubSub "chat moderator actions" topic, which made sense because other moderators should be informed of this mod action. I think at some point it also happened when allowing/denying through the website.

    Now allowing/denying through the website and the new endpoint (I think) does not provide this information to other mods. The only thing that is sometimes triggered is a channel terms action event, which is good, but it doesn't provide a direct connection to which message was affected (and it doesn't seem…

    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

    2 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. I see you have it in your v5 API https://dev.twitch.tv/docs/v5/reference/channels#reset-channel-stream-key

    But it seems like there's no way to do this in the current API? This would allow someone to create an automated channel for a community, like the Randomania channel, or the ZeldaSpeedruns channel

    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

    2 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)
  10. With the way how certain bots work, Webhooks wouldn't work with said bots. So my Suggestion is to include PubSub so more bots can utilize features like Hype Train and other stuff included on twitch.

    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

    Deferred  ·  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)
  11. 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)
  12. Add the functionality to sort Channel Points redemptions into categories (and ofc make this settabel via the API).

    It gets confusing and hard to find the redemption you're looking for with the current (amount of points based) sorting when you have one or more applications with multiple redemptions each and maybe then even some random single ones as well.

    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)
  13. I believe that updating the redemption to have a status of CANCELLED should remove any active cooldowns on the custom reward

    I understand that it needs to go into the cooldown state immediately so that other users cannot redeem it again, however setting the status to CANCELLED is our way of signalling that the event did not complete. It's how the streamer says "sorry I can't do that, have your points back".

    It makes little sense for the redemption to stay in cooldown when the custom reward has failed to be completed.

    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

    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)
  14. The webhook/response for subscriptions returns a payload as

    (webhook example)

    {
    "data": [
    {
    "eventdata": {
    "broadcaster
    id": "casterID",
    "broadcastername": "aCaster",
    "gifter
    id": "",
    "giftername": "",
    "is
    gift": false,
    "planname": "Some Subscription ($4.99)",
    "tier": "1000",
    "user
    id": "someID",
    "username": "someName"
    },
    "event
    timestamp": "2020-10-16T17:33:46Z",
    "event_type": "subscriptions.subscribe",
    "id": "1iyAnn4NpVMZ9jYv0HDOQP4SfpS",
    "version": "1.0"
    }
    ]
    }

    But it doesn't include information about if it was a 1/3/6/12 whatever subscription or not.

    Please extend the payload (for both webhooks and the API) to contain this information about if it's a multimonth purchase

    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

    2 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. Allow developers to mock responses from all common integration points- subs, bits, follows, streams, etc, and allow users to mock users as well.

    This is useful for automated testing as well as building extensions.

    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)
  16. get game followers or check if a user follows a game

    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

    2 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)
  17. This is great documentation. I'm asking if there will ever be a pubsub topic for sharing real-time viewercounts? I've noticed the get channel endpoint only updates every 15 minutes.

    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. If you have a not very tall browser.
    And you request, a fair chunk of the oAuth scopes.

    When you redirect the user to Twitch.

    The Accept/Deny link page auto jumps down to the bottom of the page.

    This means the first few/most "dangerous" scopes as well as the application name/logo and whom you are logged in as are above the fold of the page.

    Basically "suggesting" to the user not to read all the scopes and just go accept/deny.

    The auto jump to bottom of the page should be removed.

    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)
  19. On the new Helix endpoint, https://dev.twitch.tv/docs/api/reference/#get-extension-transactions and therefor https://dev.twitch.tv/docs/api/webhooks-reference/#topic-extension-transaction-created the signed receipt that comes with onTransactionComplete from the JS Helper is missing. In order to audit and avoid man in the middle attacks, a signed JWT that can only be verified with the client secret should be sent on all endpoints sending monetary transaction data.

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