81 results found
-
Disambiguate the "Legacy" API in documentation This page should mention that "v5" and the "kraken" api refer to the same thing. Me and my friends always used "Kraken" to refer to this api, it's in the endpoint its self.
I'm sure we are not alone in this, please mention that v5 IS the Kraken endpoint, you should even rename the side-section to say "Legacy Twitch API v5 (Kraken)"
1 vote -
Please revert the EventSub documentation format changes You changed the EventSub documentation between last night (Nov 16, 2021) and today (Nov 17, 2021). The new documentation is very confusing. Specifically speaking:
- The Subscription Types documentation links on the left side are out of order and like-kind events are not next to each other. For example, "Redemption Status Update" should be next to "Channel Points redeem reward".
- The Subscription Types are poor named, and it's a little difficult to figure out which Subscription Type goes to which event.
- The URL to go straight to the section in the Subscription Types is different from the type supplied in an…
1 vote -
dimensionn There's a typo under mobile guidelines:
"dimensionn"1 vote -
missing scopes Scope list says it's comprehensive, but it does not include user:read:email which is listed in some other docs.
1 vote -
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.
-
broken link the register your app link is broken
it's https://dev.twitch.tv/dashboard/apps/create
but should be
https://dev.twitch.tv/console/apps/create1 vote -
possible grammatical change on page https://dev.twitch.tv/docs/pubsub
"These example applications share a common pattern: on application load, the application fetches a complete snapshot of its state and uses a PubSub connection to receive updates to this state. The updates act as “diffs” to the initial state."
Unsure it's stated correctly as PubSub is the model but not the connection. The connection protocol is WebSocket. Should possibly read:
"These example applications share a common pattern: on application load, the application fetches a complete snapshot of its state and uses a WebSocket connection to receive updates to this state. The updates act as “diffs” to the…1 vote -
Link Scope API with capabilities Hello Twitch !
Can you please add links to api capabilities on each scope ? It would be very useful :-)Best regards
LMD1 vote -
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 -
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 -
Possible error/typo "Scopes are specified as a space-separated list in the URL scope parameter, when requesting authorization:
&scope=user:edit+user:read:email"
Space- or Plus-separated?
1 vote -
Update Docs The 200 vs. 400 result for revoking tokens is wrong, the API does actually give you a 400 with the message "Invalid Token" if you try to revoke an invalid one.
1 vote -
Incomplete documentation The scopes should be defined in more detail. For instance, from this page, I cannot tell what scope I need to view stream start time, nor can I tell where to go to find this information.
1 vote -
typo Hi might be a typo?At least it was giving me trouble till i fixed it. I am a noob so feel free to ignore. Thanks!
Line 4 in onchanged:
Try should be 'try'
?
1 vote -
Unclear Mention of Regex for Bits Parameter Hi! For the bits parameter on PRIVMSG, it's not clear to me what this means:
"The amount of cheer/Bits employed by the user. All instances of these regular expressions:
/(^|\s)<emote-name>\d+(\s|$)/"I'm just not sure what I should be using this regex on or how this fits with the example message provided.
1 vote -
Incorrect Syntax, Poor quality code, and replace screenshots with embedded code blocks - Incorrect Syntax The JavaScript code in this image is not syntactically correct: https://dev.twitch.tv/docs/assets/uploads/extension-tutorial-11.png
For example, "Try" is incorrectly capitalized.
- Example code is poor quality I referenced the example code for step 1 at: https://github.com/sonia145/extensions-101/blob/step-1/config.js
It's extremely messy with lots of lines commented out. There are about 13 commented out
console.log
statements.- Replace screenshots with embedded code blocks
This page would be greatly improved by replacing the GitHub Gist screenshots with actual embedded JavaScript code blocks.
1 vote -
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
login
for embed purposes6 votes -
[TYPO] EventSub channel.update docs Channel Update Notification Example states both
user_id
anduser_name
are returned, when actually it returnsbroadcaster_user_id
andbroadcaster_user_name
Ref: https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types#channelupdate
2 votes -
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 -
Don't mention NPM Under "Run the Chatbot Locally", npm comes with node.js. Saying to install both can be confusing when there is no download option for npm.
1 voteThanks for mentioning this! We’ve updated the instructions for today’s docs deployment.
- Don't see your idea?