160 results found
-
Move GitHub repository to official Twitch organization Please host the example code in an official Twitch organization on GitHub such as:
https://github.com/TwitchDev
https://github.com/twitchtv9 votesExample code has since been moved to https://github.com/TwitchDev
-
Documentation still outdated for helix requirements Even tho https://twitch.uservoice.com/forums/310213-developers/suggestions/40340764-add-client-id-headers-to-examples is marked as completed the docs are still 90% outta date for helix changes (According to Barry)
https://dev.twitch.tv/docs/api/guide#rate-limits still talks about not provided tokens
https://dev.twitch.tv/docs/api#step-2-sample-code still doesn't use a OAuth token
https://dev.twitch.tv/docs/api#step-3-results Is incorrect because step 2 doesn't use a OAuth token
8 votes -
Docs missing first/pagination on API's that support them From: https://github.com/twitchdev/issues/issues/19
Brief description
Many API's don't document that they support
firstandafterExpected 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 VideosMissing Pagination in the
Return Values
- Get Broadcaster Subscriptions
- Get Videos8 votes -
Document API and IRC tags for replies Web chat users got access to the new "replies" feature, where you can mark your message to be a reply of another message.
My suggestion is to add official documentation on how third parties can use this feature (for sending messages and for parsing received messages to be a reply)
7 votesThis is available in EventSub as part of channel.chat.message, and in IRC is now documented under PRIVMSG Tags
-
Clarify secure website required This should say a secure website is required. Took me 2 hours to figure out what was wrong.
7 votesThis requirement is mentioned on the Introduction to this section:
https://dev.twitch.tv/docs/embed/#embedded-experiences-requirements
-
Get users doesn't mention that an App Access Token works 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 -
Missing scope 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 -
It is unclear that "Authentication none" means "any token" Some endpoint in the docs say "authentication none" leading to some confusion
https://discuss.dev.twitch.tv/t/getting-top-games-in-python/28256/
6 votes -
broadcaster_name not noted in return values of Get Channel info 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
loginfor embed purposes6 votes -
Document correction for helix moderators endpoint 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 -
Fix or improve your API Documentation. 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 votesEarlier in the year, the API example had been fixed and the guide has been rewritten.
-
Emotes referred to as numbers, where this is no longer true The PRIVMSG Twitch Tags documententation
https://dev.twitch.tv/docs/irc/tags#privmsg-twitch-tags
says
Information to replace text in the message with emote images. This can be empty. Syntax: <emote ID>:<first index>-<last index>,<another first index>-<another last index>/<another emote ID>:<first index>-<last index>... emote ID – The number to use in this URL:Due to channel point modifications, this is no longer true, as emote's are no longer always numbers, they can be xxxx_hf for example
5 votes -
links no-longer clickable The procedures are no longer clickable at https://dev.twitch.tv/docs/authentication#getting-tokens.
(for a clickable reference see https://web.archive.org/web/20191220122144/https://dev.twitch.tv/docs/authentication)
5 votes -
don't assume gender of viewers in documentation Extensions Manager Overview -> Capabilities -> Request Identity Link
Description refers to viewer as a male ('his'). This is likely to offend some people?
5 votes -
RSS Feed of the Changelog I love that there is a changelog, would be really nice if there was an RSS feed of this however.
4 votesThis is now available: https://dev.twitch.tv/docs/change-log/#2026-03-25
-
Error in "Refreshing access tokens" section The actual docs states that "When you make a request with expired or incorrect authorization credentials, the API returns a WWW-Authenticate header (with an invalid_token error) and a 401 Unauthorized status", but the WWW-Authenticate header is not present in the response.
Moreover the example shows a kraken endpoint.
4 votes -
Update References to v5 API There are reference to V5 API here to get user and channel ID.
Combined with the GitHub Sample at https://github.com/twitchdev/pubsub-javascript-sample that is still using it this is very confusing to get to work.
Suggest to update the sample and this article to reference the helix APIs instead.4 votesDue to the deprecation of PubSub, the mentioned page has been rewritten, and the code samples have been removed from Github.
-
Capabilities sub pages no clear capability needed It should be more obvious that
Twitch IRC: Commandsneeds the commands capability,Twitch IRC: Tagsneeds the tags capability, Membership page needs the membership capability.IE:
Literally add a paragraph at the top to the effect of
The Twitch IRC responses outlined on this page requires the connection to have requested the $whatever capability as outlined on the https://dev.twitch.tv/docs/irc/guide#twitch-irc-capabilities Capabilities section of the guide.
4 votesThese pages have since been rewritten to better surface the requirements to use tags and commands:
https://dev.twitch.tv/docs/chat/irc/
-
Correct typing errors in the "Scopes" At https://dev.twitch.tv/docs/authentication#scopes
- "channel:manage:brodcast" is misspelled (should be "channel:manage:broadcast")
- "channel:manage:extension" is misspelled (should be "channel:manage:extensions")As metioned in other posts "channel:read:redemptions" is still missing there.
4 votes -
4 votes
EventSub is our Webhooks solution. We will remove the legacy Webhooks section of the docs when our Legacy Webhooks product is shut down later this year.
- Don't see your idea?