160 results found
-
bug report "Exchanging bits for a product" section has broken markdown link to /extensions/reference/#helper-bits
1 vote -
Typo A token bucketalgorithm
1 voteThis has been fixed.
-
1 vote
-
Words missing in docs Missing word(s) in this sentence:
"if the parameters supplied are you receive an immediate 202 Accepted response"
between the "are" and the "you" there's words missing.
1 vote -
formatting broken for example response Formatting broken for example response at https://dev.twitch.tv/docs/api/reference#get-hype-train-events
1 vote -
Chat embed ID parameter example/description Should the ID parameter now be "chat_embed" or the channel name? Parameter description and example code don't match or I don't understand it.
1 vote -
Documentation for 'Get Users Follows' is out of date The documentation for Get Users Follows says: “Authentication: None”, but you get “OAuth token is missing” response when not using an app or user access token.
1 vote -
Missing Client-ID in examples The recent new end points caused the existing documentation to lose the Client-ID from all other examples as is required by the changes to helix.
For Example:
https://dev.twitch.tv/docs/api/reference#get-extension-analytics
curl -H 'Authorization: Bearer cfabdegwdoklmawdzdo98xt2fo512y' \ -X GET 'https://api.twitch.tv/helix/analytics/extensions?first=5'Getting Started also needs to be updated as it doesn't reference authorization required at all
https://dev.twitch.tv/docs/api, and doesn't cover how to get authorization
1 vote -
Get Channel includes references to information not in the response https://dev.twitch.tv/docs/api/reference#get-channel-information
Refers to
statusanddescriptionwhich are not in the responseAlso mentioned in
https://dev.twitch.tv/docs/api/reference#modify-channel-information
1 vote -
Documentation layout when scrolling You scroll to the right this happens:
1 vote -
The new documentation uses a different format to the cURL examples curl --location --request PATCH 'https://api.twitch.tv/helix/channels?broadcaster_id=41245072' \ --header 'client-id: wbmytr93xzw8zbg0p1izqyzzc5mbiz' \ --header 'Authorization: Bearer 2gbdx6oar67tqtcmt49t3wpcgycthx' \ --header 'Content-Type: application/json' \ --data-raw '{"game_id":"33214", "title":"there are helicopters in the game? REASON TO PLAY FORTNITE found", "broadcaster_language":"en"}'compared to
curl -H 'Authorization: Bearer cfabdegwdoklmawdzdo98xt2fo512y' \ -X GET 'https://api.twitch.tv/helix/streams/markers?user_id=123&first=5'Examples should be consistent
1 vote -
Modify channel: oAuth confusing https://dev.twitch.tv/docs/api/reference#modify-channel-information
Says
Parameter Type Description broadcaster_id string ID of the channel to be updatedWhen it should say
User ID of the broadcaster. Must match the User ID in the Bearer token.as per
https://discuss.dev.twitch.tv/t/announcing-the-latest-helix-endpoints-and-hype-train-api/26530/12
1 vote -
Deprecated attribute frameborder is deprecated, shouldn't suggest in docs
1 vote -
Typo in docs On page:
https://dev.twitch.tv/docs/extensions/reference#helper-bitsThe 'onTransactionComplete' fields list 'transactionID' (capital D), but you get "undefined" when accessing with capital D. Actual field is 'transactionId'.
A small change, but tripped me up a bit during implementation.
Thanks!
1 vote -
IRC NAMES command only ever returns self The IRC documentation states
List current chatters in a channel. If there are more than 1000 chatters in a room, NAMES return only the list of operator privileges currently in the room.
In my testing, I have only ever gotten Twitch to return my own username, even (only) in small (under 1K) rooms.
[@] :eggdroptest.tmi.twitch.tv 353 eggdroptest = #superscientistjhrek :eggdroptest
For example, that room usually has 15-30 chatters (in this case, there were 23 people in it), and several mods, but no names other than my own were returned as part of the 353 message.My suspicion is that perhaps…
1 vote -
Thanks This is really very cool. Thank you for taking the time to create such awesome documentation. I am a front end dev for a well know travel website and I appreciate the effort that goes into making this.
1 voteThank you very much!
-
fix misleading descriptions This documentation isn't clear enough, it implies that the ID attribute should be set to the channel name, but for whatever reason it has to be set to 'chat_embed' and then the channel name goes in the SRC URL, replacing the 'hebo' text. There's no description of how the 'src' attribute should be presented so this isn't immediately clear.
1 vote -
My "documention idea" is that the documentation has a text formatting bug https://i.gyazo.com/76d10ed7c987ed262276501e25231ac6.png
"
WWW-Authenticate header" vs "WWW-Authenticateheader"EDIT: Another bug here https://dev.twitch.tv/docs/api/webhooks-reference#subscribe-tounsubscribe-from-events
"...if the parameters supplied are you receive an immediate..."
Reads like there should be something after "are".
1 vote -
Add more content to PRIVMSG Tags examples Under the PRIVMSG tags, there are some messages that only have tags and have no other message parts with it (i.e. there is no PRIVMSG, no channel, no message)
0 votes -
Placeholder "TBD graphic" label still in "Designing Extensions" documentation https://dev.twitch.tv/docs/extensions/designing still contains the text annotation "TBD graphic", where there is currently no graphic
0 votes
- Don't see your idea?