163 results found
-
Where is the name listed? "Set Name to your application's name. The name must be unique among all Twitch apps. Your app's name is listed on the Connections page under Other Connections if your app requires user consent to access or modify the user's resources." I do not understand where the name is listed, when I am on the page on which the link sends me there is not that.
1 vote -
"Make your first call" Example not working in the documentation In the get started page (https://dev.twitch.tv/docs/api/get-started) using the code provided in the "Make your first call" paragraph is not working (and also the first request to get the access token), the returned error is:
"URL using bad/illegal format or missing URL"
The error is caused by the use of the single quotation mark (') instead of the double (").
I don't know if this is a Windows limitation or something wrong with my curl version (latest from the curl project https://curl.se/windows/) but I think that this should be corrected or at least mentioned, because I wasted half…
1 vote -
Typo There's a typo on the "Running the bot" section of this page: https://dev.twitch.tv/docs/irc/get-started
The last word of the "The bot is running locally..."
It's supposed to be dice, i guess.
I don't want to roll the die lmao1 vote -
Scope delimiter needs to be explicit ':' instead of code &scope=chat%3Aread+chat&3Aedit is not correct. It needs to be: &scope=chat:read+chat:edit
1 vote -
Rate limits with different status between channels This is related to the "Rate limits" section :
What if a bot joins 2 channels, but only has mod status in 1 of them ?
Will the messages limit be 20 for both channels ?
Or will it be 20 for the channel where the bot doesn't have mod status and 100 for the channel where the bot has mod status ?
1 vote -
API Reference Typo Under the Return Values of the Get Predictions Request of the Twitch API Reference, the description of the return value 'outcome.users' has a typo. It should read 'Number of unique users that chose the outcome.' However it says 'Number of unique uesrs that chose the outcome.'
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 Typo on second bullet point of Specify Configuration Settings: access has one too many 's'
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 -
Diagrams not being rendered It looks like the diagrams/visualizations for this page are not being rendered for some reason. I'm not sure how that happens, but instead of diagrams, I'm seeing raw code that looks like it should work with Mermaid to render the diagrams. This is what I am seeing:
%% ext-twitch.tv graph TD ext-twitch.tv --> my-extension.ext-twitch.tv ext-twitch.tv --> your-extension.ext-twitch.tv1 vote -
Please add more examples for Ratelimit headers Please provide one example for the Ratelimit headers. Tried a couple of hours without success. Thanks.
1 vote -
Create EventSub Subscription Wrong Response Code On the documentation for creating an eventsub subscription the page claims a success response should have a status code of 201, but the actual status code returned on success is 202.
Either the documentation should be changed to refled the API, or the API changed to reflect the documentation.
1 vote -
documentation mismatch the linked glitch account code, twitch-chatbot
by Matt Auerbach looks for the string '!d20' in bot.js instead of the string '!dice' as indicated in this guide. caused a moment of confusion1 vote -
Update documentation on including email in userinfo endpoint claims={"idtoken":{"email":null,"emailverified":null},"userinfo":{"picture":null}}
is wrong, the email is included when including it in the "userinfo" part.
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 vote -
User-type property not described all the message examples include the property "user-type" but there is no format description of that parameter or its values
1 vote -
Typo: notificaiton Typo: notificaiton
1 vote -
ui UI follower grouping
basically, make a folder with the name and drop streamers based on desired grouping option1 vote -
Documents client flow OAuth client credentials flow
refreshtoken is not returned for clientflow as documented.1 vote -
Missing Params in OIDC I think you are missing
force_verify as an optional param on the OIDC authorize, ( its working just not documented)1 vote
- Don't see your idea?