46 results found
-
PubSub Channel Points Data Layout Cleanup Right now, most of the PubSub topics are inconsistent with each other (understandably so). This, however, is focusing on cleaning up some of the ChannelPoints event data that is either unnecessary, redundant, or unclear:
As a note, the information stripped away from the structure is not invalid data, but rather data we likely don't need per message and instead should have a fetch api like manner. One example is the image objects that are likely to never change in the lifetime of a reward. This would save needless encoding as well as any data costs there may be on either…
4 votes -
Search is missing from the Embed landing page https://dev.twitch.tv/docs/embed
is missing the docs search function top left/first item in the nav
4 votes -
Add a copy link icon to each section header Since the docs are so long, and each header has an ID you can link to, you should put a link icon that copies the link to clipboard for each header for easy sharing.
3 votes -
How to send a basic API GET request with ajax or postman Unhelpful page. I want to send an API request to test through Postman, but I do not understand what format to put it in. It is asking for an OAuth token, but that request does not mention anything about that. Very confusing.
3 votes -
Expand on V5 to Helix mappings the V5 scope 'user_read' is not listed here. In the migration document it suggests that that is equivalent to the helix scope user:read:email. Is that correct?
Is there a V5 scope that matches the new helix user:read:broadcast
3 votes -
Publish Official Typescript Typing's for all Data Models It would be very easy to build and design for if there were official typing for all data endpoints. The data between all the different API's for the same data isn't consistent, and with event sub, since it no longer relies on the underlying Helix endpoint, that data can now be different too. This will also mitigate typos on the docs which causes huge headaches when trying to code for API responses and the data not working, or missing fields. The typing can specify which fields are required and which are optional, so when designing your app, you can easily…
3 votes -
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!
3 votes -
"Build your first Extension" section lacks critical information The "build your first extension" walkthrough was perfect until about the half-way mark, then it started omitting hugely important steps. I had to stumble around to try and keep up, and although I was modestly successful, I was not able to see my Panel extension in my channel. Would have been helpful to actually have a zip file of assets to upload, because I have no idea whether I did that step correctly.
3 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"
3 votes -
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.
3 votes -
Document error responses https://dev.twitch.tv/docs/authentication/getting-tokens-oauth#oauth-client-credentials-flow
There's no information about error response and it doesn't seem to be fully compatible with RFC 6749 which means I can't find info about possible errors easily.
3 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 -
Allow Joining/Creating Multiple Organizations There are more and more cases working with different teams, especially with more and more hackathons, that the need to separate groups for different projects on Twitch have become more of a need. There were talked about a Soon™ feature to allow multiple organizations, but nothing has come about. This would be great to allow, and then allow movement of apps between personal accounts to an organization on the site once this is setup to help management, or a form to allow twitch to process the movement.
2 votes -
Game developer playbook clip not playing On https://dev.twitch.tv/gamedevelopers/development embedded clip is ot configured properly
2 votes -
Please add actual code instead of images in the documentation Please add actual code instead of images in the documentation. It would be much easier to copy it. Example: https://dev.twitch.tv/docs/tutorials/extension-101-tutorial-series/config-service
2 votes -
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
2 votes -
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…
2 votes -
Post a link to GitHub repo of full source code of tutorial "Check: If you want to see the completed code at this stage, its available on the Step 1 branch."
There are no links to the source code. It would be extremely helpful to have a link to GitHub repo with full set of code in this tutorial, to see how it all goes together.
2 votes
- Don't see your idea?