961 results found
-
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 -
Need filter by language in game clips Helix don’t have for game clip by laguage param filter.
Helix api must need it for the other country.
Thank you.
2 votes -
Denote Watch Party as a Stream Type in Get Streams Given the site shows Watch Parties as an alternative "type" to Live content (similar to Reruns), it should be denoted as such in the Get Streams API.
1 vote -
4 votes
-
Auto unsubscribe So you send a request for a subscription event
add a optional
--terminate xs
there xs is number of seconds
You send the subscription event then x seconds later automatically send the unsubscribe that has the same parameters as the subscription.
2 votes -
User upgrades a sub from x to y Whether the source sub is
- giftsub
- anon giftsub
- prime sub
- tier 1/2
1 vote -
Pop Out Extensions Should Include Same Context as Normal Panel Extensions As title states, popped out extensions should provide the same context information as normal panel extensions (for example the HLS latency).
1 vote -
Camera Overlay and Voive Off By Visitor or Spectator -Often is the Camera size to big and we can´t see the Game good.
I find New Option to disable the Camera by Spectator was Nice.
-And the same by Overlay many People will see the Game not the Face of the Streamer or the Overlay.
-Somethimes the Streamer talk to mutch or have Teamspeak on with other players and bad Voice or so .
I think the option Game sound Only was good when you will see the game.I find the First place is the Game not the Streamer profile .
1 vote -
Channel Analytics API There needs to be an API that allows for the return of channal analytics.
This would have the reqiured query parameters of: broadcaster_idOnly stating the broadcaster_id could return the following results:
- Average viewers
- Total views
- Average new followers per stream
- Total followers
- Average subscribers per stream
- Total subscribers
- Average minutes watched per stream
- Total minutes watchedIt could also return:
- Best performing catagories
- Best performing tagsThere would idealy also be some optional query parameters: start-date, end-date, time.
Adding the optional query parameters would also add the result:
-…55 votes -
Add Support for Channel Points Community Challenges Add support to access/query and maybe even create/edit/delete community challenges.
For example to unlock a big "something" in a game, when the community goal has been reached.
75 votes -
VIP scope mistake? Hey, it says "/vip /unvip" is under "channel:moderate" scope, wouldn't that be moderator status? because I'm sure moderators can't grant/remove VIP status to a user. Or am I wrong?
2 votes -
App analytics similar to extensions analytics It would be nice to have analytics for "normal" OAuth apps similar to what extensions already have.
The analytics could include authed users overall, new authed users in the past x days, xxx logins / oauth authorize per day and revokes per day. Having theses stats would make it much easier for developers to see how many users are using their apps, especially if they are client token ones without a server backend.
As bonus these analytics could also include a listing of how many request per Twitch API endpoint were done. Google for example has this in their API…3 votes -
Add a transport filter to the status endpoint It would be nice if you could filter the response of the subscription status endpoint with a transport filter (e.g. "?transport=websocket").
Its not a big deal at the moment because there only is one transport (webhooks) available but with more transports added down the line this would be a huge QoL improvement.
9 votes -
Lock created rewards? When a reward is created by the API, we should be able to prevent the streamer from being able to change values that we set. They should still be able to disable or delete the reward.
By locking the reward, we can offer a similar experience to all users and prevent confusion when one reward is drastically different from the same reward on another stream.
Just some use cases below would benefit from this.
Currently, we can set the max number of users of a reward per stream and our backend could be enforcing the same amount of rewards redeemed.…
3 votes -
Standard way of accessing full data after webhook After a webhook fires, I'm given context to the UserID and Username. In the instance of "stream.online", I would like more information. In the old webhooks, I was given the full stream data object. Will there be a standard way of accessing the full data object of whatever is "notifying" the webhook? Or is it on me to use the existing Helix API to then get that information(user info, game info, broadcast info)?
One thought would be to simply give the appropriate URL to POST to for more information, similar to how some APIs give a paginated cursor URL to…
2 votes
- Don't see your idea?