161 results found
-
Unordered Section in Authentication Docs I noticed that the section for Implicit Grant Flow has a section after it titled "Use the authorization code to get a token
" where it specifies how to use a authorization code to get the access token, but you already get the access token from Implicit Grant flow, I believe this section should not be there but instead should be at the end of the Authorization code grant flow section, just before Device Code grant flow. Because Authorization Code grant flow does not show a section on using the authorization code to get an access token.2 votes -
Missing Scope user:edit:broadcast The Twitch API Scopes list in Authentication is missing the "user:edit:broadcast" scope.
2 votes -
One language per view After providing feedback. There is the big text "Vielen dank!" I am from germany I appreciate that. But the second line is english. Please stick with one language. This is production environment. People can see that.
2 votes -
Next Step Button Hello guys, I can understand that documentation is boring but it brings a lot benefits on the long term. So please think about those two suggestions:
1) In your 101 tutorials page for example. Add an next page button.
2) Typos are made i know. I do it myself. But before publishing your guide check for typos - its your production environment. people can see this.Cheers
Patrick2 votes -
lickmaballs love you *******
2 votes -
Scope Query Parameters are incorrect In the section which refers how get an access token for the bot, the scope query parameters seem to have a typo:
current: chat%3Aread+chat&3Aedit
should be: chat%3Aread+chat%3Aedit
...or replace with a ":"2 votes -
No info about "expires_in" field in response of refresh request Hello, thanks for this great page! But there is no info about "expiresin" field when using refresh token. Refresh request returns "expiresin" field too. Am I doing something wrong?
2 votes -
Followed list to indicate subscription In your list of followed streamers, you can see which ones you have a gift subscription to. It would be great to see which channels you subscribe to in this list as well.
2 votes -
Apply for appeal Yandere Simulator Yandere Simulator has done a lot changes to since 5 years ago since its been banned including censoring blood pools, nudity and panty shots to make video streams more friendly. I recommend taking second look at game for all improvements its great game and deserves second chance. I wasn't sure to place category I apologize for that. All I'm asking is for second look at game in its current state for reconsidered banned that is all and thank you for your time.
2 votes -
Add additional examples. Add examples of popular 3rd party libraries.
The current example is very specific and only targets one language. Many community driven libraries are continuously developing and mainting IRC capablities in languages such as; Python, JS/TS, C# and more.
It would be nice in general to see more support for these libraries and even giving some sort of verfication to popular libraries that are maintained and meet quality standards.
2 votes -
Put a link to the tutorial here Where's the link to the tutorial?
2 votes -
Fix AutoMod status doc - example curl request The example curl request here:
https://dev.twitch.tv/docs/api/reference#check-automod-status
Doesn't work.1) It needs a broadcasterid query param
2) It needs the content-type header (application/json)
3) I get a 500 error using the provided "userid"s in the post body, using other user_ids worksI spent more time than I care to admit figuring this out, so it seems like fixing this will probably hep somebody out in the future.
If these three things are fixed the call succeeds.
2 votes -
Wrong User I think at the very bottom of this page you meant to write User C because that's what that paragraph is talking about.
2 votes -
Sample code in the Status section is mac only. Sample code for windows users would be awesome!
2 votes -
If I need Extensions Onboarding, link to it. You have error messages that tell me I can't do [insert a variety of things here] until I have completed something like "Extensions Monetization Onboarding." The error message fails heuristics because it doesn't let me fix the problem. It says I need to do something but doesn't give me a link or way to do it. That seems like a huge mistake, but with the forums FULL of people complaining that they can't find it either, I'm wondering if it's a dark pattern and done on purpose.
If there is a workflow that requires me to move through certain steps,…
2 votes -
Fix the example GitHub repo to better correlate to the documentation on this page Provide a link to the referenced branch associated with each step.
There are no branches for steps 3 and 4. The existing branches don't correlate to the code presented for each step on this page.
And there's messy commented out code in all of the files on GitHub.Also, 4 steps are explained, and then the last sentence in this doc mentions the Step 1 branch
2 votes -
Add common (and uncommon) error responses from API request I received an error I have never seen before and it got me thinking it would be nice to have some documentation on various error messages like "Insufficient authorization in token". Other errors are clear and straight forwards like "missing X scope" however some are vague and unclear.
2 votes -
Improve documentation for WebHooks' hub.secret property The hub.secret property needs far more explaining of how the secret is generated:
"The X-Hub-Signature header is generated by sha256(secret, notification_bytes)"
It should say something along the lines of
"The X-Hub-Signature header is generated by using HMAC sha256 with the provided secret being the one specified in hub.secret: hmac(sha256, hubsecret).hash(notificationbody)"
2 votes -
Game developer playbook clip not playing On https://dev.twitch.tv/gamedevelopers/development embedded clip is ot configured properly
2 votes -
onTransactionComplete trigger result unclear The use of bullet points reads and the "and" tacked onto the end of the first bullet point makes it unclear
The wording should be revised so it's more obvious that "onTransactionComplete" is to be sent to instances where the userID matches the userID that initiated.
Since the first bullet point is superflous, since the userID of the first bullet point is also matched by the second bullet point.
2 votes
- Don't see your idea?