76 results found
-
Clarify read-only nature of IRC MODE command While you do a good job of stating that the IRC interface deviates from the RFC, as well as where and how it deviates from the RFC, it may be beneficial to specifically call out the deviation that the MODE command is server-generated (read only), instead of being a keyword that can be generated by a client.
In other words, my bot cannot issue its own "MODE #channel +o nickname" command via the IRC interface (like it can on IRC), it can only receive notifications from the server that the server has sett one of those modes. One sentence covering…
2 votesMODE has since been removed from Twitch's IRC
-
local-test only gives test for panel extensions Doesn't give a method for testing video overlay extensions
1 vote -
Undeclared Variable an undeclared variable:
function parseCommand(rawCommandComponent) {
let parsedCommand = null;
commandParts = rawCommandComponent.split(' ');should be "let commandParts = ..."
1 vote -
Error on retrieving hmac message At the full example code, the raw body needs to be passed through the JSON.stringify(<body>) function at the getHmacMessage function since the request is part of the espress.Request class. Or that's what worked for me.
1 vote -
Wrong header in Example request of update redemption status API reference The Example Request in Update Redemption Status API reference contains wrong header. The Client-Id is named as client-id. A small typo error wasted my hour. But yep hopefully it gets fixed for others.
1 vote -
PubSub docs mention "relatime viewer count", but no such topic is present The Introduction section mentions "pushing real-time viewer count updates to video players", but the Topic section mentions of no such way. This is just tiny bit confusing.
1 vote -
Typo on Pubsub doc page Under the title: Example: Channel Points Event Message
In the description for the "status" property of a redemption message:
reward redemption status, will be
FULFULLED if a user skips the reward queue, UNFULFILLED otherwiseFULFULLED should be FULFILLED.
1 vote -
Missing details for using the recommended approach In the 'next steps' sections it mentions:
To authenticate your chatbot in a production setting, we recommend you register your app (chatbot) and use the OAuth Authorization code flow. This enables you to authenticate programmatically. To learn more, see the Apps & Authentication Guide.
I have created the app and can get the token, but have no idea what to use for the nick / pw. Since this is the recommended way, would much prefer an example or details on this rather than the login-as-user given currently.
1 voteThe mentioned example no longer uses IRC
-
Documents client flow OAuth client credentials flow
refreshtoken is not returned for clientflow as documented.1 voteClient Credentials now generates an expiring token
-
add extensions equivalence in migration page could you add the extensions equivalence?
1 vote -
PubSub Documentation Formatting In the subscription fields definition, both cumulativemonths and streakmonths are listed as strings when they are very clearly integers.
Further, it would help greatly with readability if the fields were listed in the order they appear in the supplied JSON snippets.
1 vote -
make the docs better and more simple to understand for new users. this site is awfull cause the explenation of the api is trash.
1 vote -
Pubsub Docs: benefit_end_month This evening I received a resub over pubsub for 3 months in advance. Rather than the documented "multimonthduration" field, that was set to 0 and a new "benefitendmonth" field was returned. This can be used to calculate the number of months, but I can't find any mention of it in the developer docs.
1 votePubSub was decommissioned on April 14, 2025, and no new features are planned for it.
-
Render issue in documentation The structure on how the extension and the Twitch platform communicate with each other is not rendered and only shows the raw (mermaid) input.
The title for the section is "How do Extensions work?"1 vote -
Add more information How do I get the authroization id? I can't find that anywhere. I have a client id now but running the example command results in a 401 invalid oauth token
1 vote -
email claims missing Although I set
user:read:emailin the requested scope, neither the ID JWT nor the userinfo contains the email claim. What must we do to make this take effect?1 voteThis should since be resolved. Please let us know if this issue persists by opening a Github ticket on https://github.com/twitchdev/issues/issues
-
Non-Extensions PubSub topics also are supported. https://dev.twitch.tv/docs/extensions/reference#helper-viewer
states for the "twitch.ext.listen" function/callback
Non-Extensions PubSub topics also are supported.
This is no longer true as every non extension pubsub topic requires an Authentication token, and the listen function doesn't provide a way to specify a token.
Or the documentation is unclear on how/which non extension pubsub topics are supported
1 voteRegular PubSub is now deprecated, so this issue should not be relevant anymore.
-
Wording changes You can redeem Channel Points for two types of rewards, Automatic and Custom.
Becomes: Viewers can redeem Channel Points for two types of rewards, Automatic and Custom.
SPACER
Custom Rewards are streamer-created benefits specific to the channel that generally require the streamer to take some action to fulfill them.
Becomes: Custom Rewards are creator-created benefits specific to the channel that generally require the creator to take some action to fulfill them.
Note: Creator is more on "brand" here with other parts of Twitch? as apposed to stream/broadcaster
SPACER
This API allows applications
note: so an extension can't?
Becomes: This API…
1 vote -
Missing client_secret failed curl windows/wsl/cmd This POST request - if attempted with curl in CMD or windows subsystems linux, you need to escape &clientsecret &granttype with preceeding escape\
e.g.
otherwise you WILL get missing client_secret regardless what you try, nothint about the actual curl gives you any hint regarding this.
1 vote -
Documentation issue or Google Forms issue Request api rate limit is not possible but mentioned in the documentation as of Mon, Aug 24, 2020.
1 vote
- Don't see your idea?