127 results found
-
Authentification desctription isn't descriptive enough Description in "Getting tokens" isn't very clear and missing a link to "Getting Tokens: OAuth", where it's all explained in detail. That does confuse people
1 vote -
Update the page This page seems extremely out of date and the example deep links given don't work on tvOS.
1 vote -
Complete Response Codes in Twitch Docs It would be great if we could have a list of the status codes and their reasons so we can write code to prepare for handling those errors, instead of logging them and dealing with them as they happen - for all endpoints. These exist, for the most part, in a lot of the newer endpoint documentation, but a lot of the older endpoints were rushed in their documentation and we have little information on what responses to expect. Sometimes we get 200s, 202s, 400s, 410s - and having to just "wait" or try to plan for them is a…
1 vote -
Missing docs on OAuth for initial step by step guide The step by step guide does not reference OAuth tokens yet they are required to do an API request, please update the guide to include info on this.
1 vote -
Inaccurate info in instrcutions It appears that the Glitch file has been changed! I couldn't get the !dice command to work, until i figured that the command had been changed to !d20 along with the number of sides changed to 20. Or maybe this was a ploy.... to help me understand coding better... Thanks!
2 votes -
Please add an example payload of a resubgift/anonresubgift to the PubSub docs I raised https://twitch.uservoice.com/forums/310213-developers/suggestions/41016568-context-resubgift-in-resub-events?tracking_code=8f96eb083a992136c313fb0ca1d79054 because I ctrl+f'ed for context as apposed to ctrl+f-ing for resubgift.
Please add an example for a resub/anonresubgift
4 votes -
Documentation is misleading The example and/or documentation of the "Channel Points Event Message" seem to be wrong/misleading, because the example reply does not match the structure of "Message Parameters: All Messages"
2 votes -
Modify Channel Information says "Query parameters" example post says JSON blob https://dev.twitch.tv/docs/api/reference#modify-channel-information
The example calls uses JSON, but the documentation talks about Query String/URL encoded form.
Docs should cover both possibilities and examples should cover both methods
2 votes -
anonsubgift, anonsubmysterygift, anongiftpaidupgrade are documented but never occur https://dev.twitch.tv/docs/irc/tags#usernotice-twitch-tags documents anonsubgift and anongiftpaidupgrade. I found this announcement post https://discuss.dev.twitch.tv/t/anonymous-sub-gifting-to-launch-11-15-launch-details/18683 saying that apparently it was temporarily disabled as a workaround. As far as I can tell to this day the workaround is used. The documentation should be updated to remove the originally planned but never put into service types, and instead document that anonymous gifts come from AnAnonymousGifter.
3 votes -
Embed documentation doesn't mention the SSL requirment https://dev.twitch.tv/docs/embed/ and it's child pages mention the requirements for parent but never SSL
2 votes -
Remove jQuery from the GA Example The examples for Google Analytics suggest using jQuery. Which is extra bloat if an extension hasn't use jQuery to start with and can lead to confusion
3 votes -
Chat and Pubsub - channel:moderate As per this other uservoice
The moderation actions PubSub at time of writing requires a key from the channel you wish to listen to with the scope
channel:moderateHowever the scopes page
https://dev.twitch.tv/docs/authentication/#scopes
is mis leading as it only talks about how the scope works for chat leading to confusion with pubsub operation
"Perform moderation actions in a channel. The user requesting the scope must be a moderator in the channel."
The wording needs to be changed and/or the pubsub topic adjusted to support being able to read moderator events as a moderator
3 votes -
Clarify secure website required This should say a secure website is required. Took me 2 hours to figure out what was wrong.
5 votes -
More information about 'id' uniqueness More information is required about the uniqueness of id. Is it unique forever (i.e. there will never be two messages with the same id) or is it just guaranteed unique within a timeframe?
1 vote -
error in documetation msgid:"usageuntimeout" states:'Usage: “/raid <username>” - Removes a timeout on a user.' and not /untimeout
1 vote -
Nsjsns اريد الدخول بدون تسجيل
1 vote -
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
4 votes -
Add .env files in the Managing Extension Secrets section Another way to manage an extension secret is to use a .env file. The .env file can be used to store all kinds of secrets, tokens, and passwords.
eg: TOKEN=testT0K3N
note: .env is a shell file so there can't be spaces around =
1 vote -
Link to locustfile for load testing extensions not working The formatting of the link to the locustfile in https://dev.twitch.tv/docs/extensions/load-testing-extensions#run-your-locust-test is not working because there are code tags in front of and after:
1 vote -
Fixed position or better visibility for important announcements As per a request from Barry, it would helpful if any flagged messages on a page were fixed or visible when loading a bookmarked section. For example, right now there is an important message on the API reference page about OAuth requirements for Helix, but if someone goes directly to https://dev.twitch.tv/docs/api/reference#get-streams, they will not see this message currently.
1 vote
- Don't see your idea?