71 results found

1. Procedure is wrong

   I do all of this, but I still get the following response from the server: <html>
   <head><title>400 Bad Request</title></head>
   <body>
   <center><h1>400 Bad Request</h1></center>
   </body>
   </html>

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

   Hi, please reach out to our developer support for further assistance:

   https://dev.twitch.tv/support

2. Have a responsible disclosure mechanism

   I've been trying to report a security issue (one that allows creation of thousands of accounts in under 5 minutes) for two months now.

   Support just sends me form emails and closes the ticket.

   Provide a way to talk to someone more technical than whatever the heck your support is.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  1 comment  ·  API  ·  Delete…  ·  Admin →

3. Wrong Followers Counter

   Hey there,

   I would like to let you know that in Get Channel Followers API Endpoint the total value, Follower Goals everywhere, Follower Counter everywhere are showing the wrong number.
   It is not noticeable, because its shows the follower list length minus one, but logically it is incorrect.

   E.g.: I have 194 followers on these counters but if I query my follower list via the API, then I'll get an array of 195 items without duplicates. Also if I go to the streamer dashboard's follower list then I also count 195 tiles despite of the 194 follower count.

   It's not a big issue, but still that is incorrect.

   Hey there,

   I would like to let you know that in Get Channel Followers API Endpoint the total value, Follower Goals everywhere, Follower Counter everywhere are showing the wrong number.
   It is not noticeable, because its shows the follower list length minus one, but logically it is incorrect.

   E.g.: I have 194 followers on these counters but if I query my follower list via the API, then I'll get an array of 195 items without duplicates. Also if I go to the streamer dashboard's follower list then I also count 195 tiles despite of the 194 follower count.

   It's not… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  0 comments  ·  API  ·  Delete…  ·  Admin →

4. A full list of current viewers please!

   Is there no way to get a full list of all your current viewers? I would love to check to see who of my current viewers are subscribed to me. This is killing me, please help!

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  API  ·  Delete…  ·  Admin →
   Closed  ·  AdminJon Bulava (Developer Relations, Twitch) responded

   Potential solution provided in comments.

5. Make things easier.

   The new API changes are way too complicated. I can't use my new followers api add-on now and it tells me I can still use it with the new changes but does a ton of techno babble about api, which I don't even know what that is or how to change it. Now my entire ability to track who new followers are is completely gone and there's zero way to track it, it's way too complicated and hard. Make it so it's easy and you can just click a single button to re-enable it.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  0 comments  ·  API  ·  Delete…  ·  Admin →

6. API IGDB

   Prove the api of igdb

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

   The IGDB API is available here: https://www.igdb.com/api

7. add followers count to user or channel

   the old kraken channel object offered an follower count. I don`t find any follower count on the new helix channel or user object.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  2 comments  ·  API  ·  Delete…  ·  Admin →

8. Adding user history names or ID on Twitch

   Some services like Streamelements rewards viewers on streamer's channel with points for watching stream. If you would change your Twitch username, channel points will be reset to 0 because service unable to identify who you are (something like you are new) but still remembering old nickname.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  2 comments  ·  API  ·  Delete…  ·  Admin →

9. Missing endpoints from v5

   There does not seem be an equivalent for v5's chat endpoints. In particular, there does not appear to be an endpoint for getting all emoticons such as https://api.twitch.tv/kraken/chat/emoticons.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  API  ·  Delete…  ·  Admin →
   Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

   The v5 API has since been deprecated

10. Missing information

    Okay, I got the user access tokens... not how to use it? The page ends without a word...
    (like how to get what user is the one who accepted the request).
    Also the scope list is not full - Discord use other roles as well, not mentioned in that docs.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Closed  ·  0 comments  ·  API  ·  Delete…  ·  Admin →

11. Code in Sample 2 doesn't work, not even with freshly created credentials and app tokens.

    Code in Sample 2 doesn't work, not even with freshly created credentials and app tokens.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Closed  ·  0 comments  ·  API  ·  Delete…  ·  Admin →

12. Edit request

    The hub.challenge query param is now called hub_challenge and should be renamed in the docs

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Closed  ·  2 comments  ·  API  ·  Delete…  ·  Admin →

13. Give developers access to GQL and the full suite of actions.

    I'm aware that this is a duplicate but I feel that the answers given have been unsatisaftory, GQL is a well-known and understood standard, hence the tmi.js API would not be needed anymore, nor would other twitch-specific packages. There is no reason not to give access to this given that we all know that it's in use internally and that the security requirements would be no different.

    I think that enabling this and managing it safely would be far more secure than it remaining undocumented as developers will use the GQL endpoints no matter how much their use is discouraged as we want to push the platform further and integrate deeper into Twitch, increasing our investment, and that of streamers.

    It would also reduce work for the Twitch dev team as there will only be one API to maintain, test and keep up to date and as stated before there would be no need for specific twitch clients (either twitch-maintained or community-maintained.)

    I'm aware that this is a duplicate but I feel that the answers given have been unsatisaftory, GQL is a well-known and understood standard, hence the tmi.js API would not be needed anymore, nor would other twitch-specific packages. There is no reason not to give access to this given that we all know that it's in use internally and that the security requirements would be no different.

    I think that enabling this and managing it safely would be far more secure than it remaining undocumented as developers will use the GQL endpoints no matter how much their use is discouraged… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Closed  ·  1 comment  ·  API  ·  Delete…  ·  Admin →

14. Add Process to Get Access to GQL

    Currently, GQL is, as far as we know, for first-party and authorized developers only, but its unclear how anyone can gain access to use GQL under proper Twitch authority. There are tons of functions and features in GQL given it helps power Twitch that could aid many developers in building incredible tools to fill gaps in communities. A few immediate items that come up that could be solved very quickly (while we wait for public endpoints):
    -Adjust the Role Manager (Add/Remove Mods, VIPs, Editors)
    -Remove & Rename Clips
    -Action Channel Redemptions including Accept and Reject, get Redemption Data including Pending Redemptions

    There are plenty more opportunities that hundreds of developers would be able to come up with. I understand why GQL isn't publically available, but we have no description of how we can create an opportunity where we can use this API to aid our clients and help the Twitch Community - we're just left with an answer all the time of "third party devs can't use GQL".

    We would appreciate the opportunity to at least be able to have knowledge on how we can create this opportunity. Thank you!

    Currently, GQL is, as far as we know, for first-party and authorized developers only, but its unclear how anyone can gain access to use GQL under proper Twitch authority. There are tons of functions and features in GQL given it helps power Twitch that could aid many developers in building incredible tools to fill gaps in communities. A few immediate items that come up that could be solved very quickly (while we wait for public endpoints):
    -Adjust the Role Manager (Add/Remove Mods, VIPs, Editors)
    -Remove & Rename Clips
    -Action Channel Redemptions including Accept and Reject, get Redemption Data including Pending… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Closed  ·  1 comment  ·  API  ·  Delete…  ·  Admin →

15. offline image

    How to change channel background image with the api?

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Closed  ·  1 comment  ·  API  ·  Delete…  ·  Admin →

16. Inconsistency between Channel Points API and PubSub Redemption Topic

    When PubSub returns rewards, it references channel_id whilst the Beta API Endpoints call it broadcaster_id.

    As a Developer, i prefer to be able to parse the same object from different sources in the same way. The discrepancy in naming prevents this / makes it slightly less performant as a distinction needs to be made.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

    PubSub was decommissioned on April 14, 2025, and no new features are planned for it.

17. No me deja ver en vivo telemundo

    quiero ver mi novela

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Closed  ·  1 comment  ·  API  ·  Delete…  ·  Admin →

18. Add GET https://api.twitch.tv/extensions/<client ID> as a documented endpoint

    If you call GET https://api.twitch.tv/extensions/<client ID> you get a JSON back with the information about the extension. This is currently undocumented, but it would be a real useful took for discoverability and management, but being undocumented, it wouldn't be wise to use in a production environment. If this endpoint is planned to be kept, can it be added to the documentation for our use?

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

    This endpoint no longer exists

19. Create API to confirm/deny points rewards after processing of the PubSub message

    We need an API (probably a helix endpoint) to programmatically mark point rewards as confirmed/executed or denied if a bot who listens to the PubSub automatically processes that event.

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    Closed  ·  AdminJon Bulava (Developer Relations, Twitch) responded

    Duplicate of https://twitch.uservoice.com/forums/310213/suggestions/39903652

20. Subject: Bug Report: channel.follow v2 EventSub WebSocket Not Sending Notifications Subject: Bug Report: channel.follow v2 EventSub WebSock

    i dont know where i can post this but i just want to report this

    Subject: Bug Report: channel.follow v2 EventSub WebSocket Not Sending Notifications

    Subject: Bug Report: channel.follow v2 EventSub WebSocket Not Sending Notifications

    Dear Twitch Developer Support,

    I am reporting a bug in the EventSub API where channel.follow v2 subscriptions over WebSocket are not delivering notifications, despite being correctly configured and enabled.

    ---

    SUMMARY

    When subscribing to channel.follow events via WebSocket transport, the subscription is created successfully and shows status "enabled" in the API. However, no notifications are received when users follow the channel. In contrast, other EventSub subscriptions (such as channel.chat.message) on the same WebSocket connection work correctly.

    ---

    TEST ENVIRONMENT

    Bot Account:
    - Username: mupongpongbot
    - User ID: 1535275845
    - Role: Moderator of target channel

    Broadcaster Account:
    - Username: musicfortheworld__
    - Broadcaster ID: 1536964012

    Test Account Used for Follow:
    - Username: musicrelaxationandhealing (brand new account, never followed before)
    - User ID: 1539409101

    ---

    OAUTH SCOPES

    The bot's OAuth token includes these relevant scopes:
    - moderator:read:followers ✓
    - moderator:read:moderators ✓
    - moderator:read:chatters ✓
    - user:read:chat ✓
    - user:write:chat ✓
    - user:bot ✓

    ---

    STEPS TAKEN

    1. Created EventSub WebSocket session

       • Session ID: AgoQDh0I7VS6Saar41kPxTTWhRIGY2VsbC1h
       • Status: Connected ✓

    2. Subscribed to channel.follow v2 with correct conditions:
       json
{
"type": "channel.follow",
"version": "2",
"condition": {
"broadcaster_user_id": "1536964012",
"moderator_user_id": "1535275845"
},
"transport": {
"method": "websocket",
"session_id": "AgoQDh0I7VS6Saar41kPxTTWhRIGY2VsbC1h"
}
}


    3. API Response confirms subscription is enabled:
       
Type: channel.follow
Version: 2
Status: enabled
Transport: websocket
Session ID: AgoQDh0I7VS6Saar41kPxTTWhRIGY2VsbC1h
Condition: broadcaster_user_id=1536964012, moderator_user_id=1535275845


    4. Verified channel.chat.message works on same WebSocket:
       json
{
"metadata": {
"message_type": "notification",
"subscription_type": "channel.chat.message",
"subscription_version": "1"
},
"payload": {
"event": {
"broadcaster_user_id": "1536964012",
"chatter_user_id": "1539409101",
"message": {"text": "232323"}
}
}
}


    5. Had test account (musicrelaxationandhealing) follow the channel

    6. Confirmed follow was recorded in API:
       
GET /helix/channels/followers?broadcaster_id=1536964012
Response shows: musicrelaxationandhealing is now a follower with followed_at timestamp


    7. Expected: WebSocket notification for channel.follow event
       Actual: No notification received

    ---

    VARIATIONS TESTED

    ✓ Tested with brand new account (never followed before)
    ✓ Tested after waiting 10+ seconds for subscription to propagate
    ✓ Tested removal of moderatoruserid → API rejected with "moderatoruserid failed on 'required' tag"
    ✓ Tested on same WebSocket session that successfully receives chat messages
    ✓ Verified follow exists in /helix/channels/followers endpoint
    ✓ Confirmed bot is moderator of channel
    ✓ Confirmed bot is follower of channel (in followers list)

    ---

    ISSUE DETAILS

    The problem appears to be one of the following:

    1. WebSocket Limitation: channel.follow v2 EventSub notifications may not be supported over WebSocket transport, despite the API allowing subscriptions to be created.

    2. Parsing Bug: Twitch may be sending follow notifications that TwitchLib is not parsing correctly.

    3. Permission Issue: There may be an undocumented permission requirement or condition preventing notifications from being sent.

    ---

    REQUEST

    Could you please:

    1. Confirm whether channel.follow v2 notifications are officially supported over WebSocket transport
    2. Investigate why the subscription shows "enabled" but never delivers notifications
    3. Clarify if there are any known limitations or bugs with channel.follow v2 WebSocket subscriptions
    4. Suggest whether REST webhooks are required for channel.follow events instead of WebSocket

    ---

    Thank you for your assistance in investigating this issue.

    Best regards

    i dont know where i can post this but i just want to report this

    Subject: Bug Report: channel.follow v2 EventSub WebSocket Not Sending Notifications

    Subject: Bug Report: channel.follow v2 EventSub WebSocket Not Sending Notifications

    Dear Twitch Developer Support,

    I am reporting a bug in the EventSub API where channel.follow v2 subscriptions over WebSocket are not delivering notifications, despite being correctly configured and enabled.

    ---

    SUMMARY

    When subscribing to channel.follow events via WebSocket transport, the subscription is created successfully and shows status "enabled" in the API. However, no notifications are received when users follow the channel. In contrast, other EventSub subscriptions… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  API  ·  Delete…  ·  Admin →
    Closed  ·  AdminMarc Szanto (Admin, Twitch) responded

    This forum is for feature requests and suggestions. Please report bugs to https://github.com/twitchdev/issues/issues