1035 results found
-
Expose endpoint for total points a user has I would like an option to return the amount a points a current user has.
2 votes -
Split the Helix API reference into sub-categories As the Helix API reference page (https://dev.twitch.tv/docs/api/reference) is continuing to grow it it is starting to become unwieldly with the number of entries.
It would be beneficial to the docs to create sections for different areas of the API. Appropriate names for the sections are already listed in the API, as at the top of the reference page is a table that has a 'Resource' column which would be perfect for this usage, and that table can remain at the root reference page so that devs can see at a glance what endpoints are in what section, then…
3 votesThis has been on the roadmap, and is planned for early 2021.
-
Error 500 with update reward (is_max_per_user_per_stream_enabled) When I try to update "ismaxperuserperstreamenabled" of a reward, I get an Internal Server Error.
1 vote -
Add flag to suppress chat notification upon redemption When you have an application that uses channel points quite a lot and also reacts to them and does things, the chat is spammed with the redemption notifications which can negatively affect the chat experience.
I suggest adding a flag to custom redemptions that prevents the chat notification from being sent.
6 votes -
Allow Unicode characters for Oauth Client / Application Names Currently, when a non-Englisch Character is entered into the "Name" Field of the Application Settings (https://dev.twitch.tv/console/apps/<CLIENTID>), it is denied with the Error Message saying that the word "Twitch" is not allowed, even if that is not entered.
1) This Error Message is confusing as it is incorrectly describing the situation.
2) For some usecases, Non-English Characters would help for Names - such as German Companies with umlauts (öäü) in their name.I acknowledge that allowing the entire Unicde / UTF-8 subset can pose issues, but It makes it so an Application Name may not be 100% identifying of…
1 vote -
Batch Updates for Custom Rewards I have a system that checks what scene the creator is in, to see if that custom reward is allowed (we do scene whitelisting). A planned feature is to disable and enable custom rewards based on the scene, so that the end users (the viewers) only ever see custom rewards that will actually work.
It would be very helpful if I could batch my update calls so that I could set several rewards as disabled/enabled at once. Without this ability its very likely I'd hit a rate limit.
1 vote -
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 -
Add categories to the Channel Points list on a channel Add the functionality to sort Channel Points redemptions into categories (and ofc make this settabel via the API).
It gets confusing and hard to find the redemption you're looking for with the current (amount of points based) sorting when you have one or more applications with multiple redemptions each and maybe then even some random single ones as well.
5 votes -
Cheering Bits programmatically Cheering Bits is the most famous way to support a streamer. However, it can be somewhat challenging for new users to get familiar with the Twitch Chat commands to properly do so.
I propose an API which allows to trigger a regular cheer.
This call obviously should not be signed instantly, but sandboxed where the Twitch backend requires a "Yes / No" response via GUI from the user.I think this can improve the user experience a lot and it can also improve the general usage of Twich Bits.
For instance, many streamers use overlays in their stream to react…4 votes -
Allow request clips/videos with broadcaster_id AND game_id Allow to request clips/videos on multiple required query paramters (broadcasterid & gameid).
Exemple: https://api.twitch.tv/helix/clips?broadcaster_id=xxxxxxx&game_id=xxxx
2 votes -
Update the dashboard to mark a reward as being from "an integration" The page at
https://dashboard.twitch.tv/u/barrycarlyon/community/channel-points/rewards
Will list all rewards.
But it's not super obvious which rewards "I made" or which rewards "an API call" made.
So in theory a streamer not paying attention could delete an integration created reward.
I'm not saying "remove" the delete button, just add additional wording
4 votes -
Incomplete/Incomprehensible Step? why does the documentation not specify how the extension is including the common.js script? How is common.js capable of knowing DOM-elements that are in panel.html?
1 vote -
Show a more meaningful error message when you try to spend bits on your own channel Currently if you try to use a bits enabled extension on your channel, you get an error message that reads "Sorry, something went wrong. Please try again."
This error message makes it seem as though this action should work and that "something actually went wrong". When in actuality, they are trying to perform an action that is not allowed, that will never work no matter how many times they try again.
My proposal is to provide the user with a more meaningful error that informs them that they can't do this action because they aren't allowed to spend bits on…
1 vote -
Helix followed channels end-point should show if channel is live Currently requires two un-needed requests https://dev.twitch.tv/docs/api/reference#get-users-follows and https://dev.twitch.tv/docs/api/reference#get-streams
(Instead they could just include a ‘live’ parameter in the first request.2 votes -
Status CANCELLED should remove the cooldown on custom rewards I believe that updating the redemption to have a status of CANCELLED should remove any active cooldowns on the custom reward
I understand that it needs to go into the cooldown state immediately so that other users cannot redeem it again, however setting the status to CANCELLED is our way of signalling that the event did not complete. It's how the streamer says "sorry I can't do that, have your points back".
It makes little sense for the redemption to stay in cooldown when the custom reward has failed to be completed.
5 votes -
Examples Add extra details on examples about how to do request this topic. Your examples wrong or missing.
1 vote -
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 -
IRC Landing page/guide -> twitchapps.com https://dev.twitch.tv/docs/irc
As a getting started/IRC docs landing page is confusing new developers
As it references
The token to authenticate your chatbot with Twitch's servers. Generate this with https://twitchapps.com/tmi/ (a Twitch community-driven wrapper around the Twitch API), while logged in to your chatbot account. The token will be an alphanumeric string.
And doesn't reference anything about the "right way" to auth/scopes needed
Until the end of the guide.
Authentication using not a third party site should be more prevalent in the guide.
3 votes -
Add follow notification flag to Helix The follow notification flag is very helpful for loyalty bots to reward users for having notifications turned on. Notifications are a huge part of having users re-engage the broadcaster, and being able to reward that will bring more viewers to the stream. This was present in Kraken, but not in Helix.
10 votes -
If a user authenticates using an App Access Token, add CORS headers With the helix oAuth requirements
It is often a problem for the less experienced developer to get started, as they don't understand certain rules and limitations around the API.
The less experienced developer may then choose to generate and leak their client secret, or app access tokens on their "front end only" websites in error.
So I propose that if the token is identified as App Access/Client Credentials, Twitch adds "CORS Headers" to block the request
Consider also CORS headers to the token fetching endpoints for App Access generation as well?
6 votes
- Don't see your idea?