857 results found
-
"Registering your App" an Extension is also an App https://dev.twitch.tv/docs/authentication
Says
Authentication involves: Registering your app to obtain a client ID and client secret. Getting a token. This includes specifying scopes, the permissions your app requires. Sending the token in your API request, to authenticate API requests.But doesn't mention that an Extension is also an Application
This docs fix would be needed on other pages where "registering an app" is mentioned
2 votes -
Add ban status to the extension JS helper In a similar fashion to
it would be beneficial to include ban status in the extension JS helper. To save an Frontend->EBS->API round trip to obtain this data.
It would be a boolean unlike substatus which is null/object
Optionally useful to provide data if a active timeout is in place.
A "onBan" callback might be useful (which would only listen to to that users ban status change(s)
2 votes -
Document exact what triggers `viewer.onChanged` https://dev.twitch.tv/docs/extensions/reference#helper-viewer
SNIPPET STARTS
onChanged
Twitch.ext.viewer.onChanged: void function(callback: Function())This function binds a callback will be invoked when the viewer’s status changes (e.g. if a viewer subscribes and changes their subscription status).
SNIPPET ENDS
Cannot tell if broken or only triggers on subscription status change.
IE is it supposed to trigger on
rolechanges? If so it's bugged, if not the documentation needs to document what does cause onChanged to be called2 votes -
Viewer Data Storage for Extension Overlays/Components/Panels In the context of a Twitch Extension Overlay, the API needs a way to set key value pairs for viewers of a channel not using cookies. Chroma incognito blocks setting local storage and cookies. This would be used to store overlay settings like widget sizes and positions. That way when the page refreshes, the overlay elements would persist their placements. As the great BarryCarylon said "... like Redis for Twitch Extensions".
2 votes -
Allow 'Continue' or 'Next Page' on Tutorial The tutorials just leave you at the end of a page with no 'Continue' or 'Next Step' button. It 's not obvious if I'm at the end of the tutorial or not.
2 votes -
Clone Custom Reward The ability to specify an existing reward that exists as a basis on creating a new reward would be useful. (This would clone the image/other set parameters as well to the new reward)
Use case:
Channel points to pick a "team" the user would be in.
Today there are three teams, so clone the pre set (disabled) one three times.
Tomorrow there will be four, so clone four times.Image would be the same for all four.
2 votes -
Custom Rewards limit? Pagination Support
None.
There is a limit of only 50 Custom Rewards on a channel at a time.It's unclear if that means 50 active rewards or 50 total rewards. It should be more plain text/clear.
The help article
https://help.twitch.tv/s/article/making-the-most-of-channel-points?language=en_US
doesn't mentioned this limit either.
2 votes -
Userstate in IRC is out of date in docs This is out of date. Update it please.
2 votes -
Provide a Helix endpoint to list reward templates created by user, and eventually see the (done, claimed, refunded) I would like to have a way to access a list of CHANNEL REWARDS available for a given channel. Without authentication would be nice, as anyone can see it in the website regardless.
Another additional data provided if the API call is authenticated with the said channel, would be to see the status of the claims (Accepted, pending, refunded) so that the projects based on those can know if it was accepted or if it can be safely removed, in case of a refund.
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 -
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.
2 votes -
2 votes
-
Inconsistency between Channel Points API and PubSub Redemption Topic When PubSub returns rewards, it references
channel_idwhilst the Beta API Endpoints call itbroadcaster_id.As a Developer, i prefer to be able to parse the same object from different sources in the same way. The discrepancy in naming prevents this / makes it slightly less performant as a distinction needs to be made.
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 -
Add overlay info to the player embed state We really need a way to determine what overlays display to the user so we can handle them gracefully. For example, we have no way of knowing when the mature overlay displays and this negatively affects our channel discovery UX.
2 votes -
Asymmetric JWT Signing Can we have the option for asymmetric JWT signing? I want to validate JWTs sent by twitch on publicly accessible software.
2 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?
2 votes -
error in documetation msgid:"usageuntimeout" states:'Usage: “/raid <username>” - Removes a timeout on a user.' and not /untimeout
2 votes -
inmediatly send the the drop to the inventary after you watch the stream for 2 hours for example the valorant beta
2 votes
- Don't see your idea?