436 results found
-
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 -
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 -
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 -
Extend Subscription Webhooks/API to return information about multi month purchase The webhook/response for subscriptions returns a payload as
(webhook example)
{
"data": [
{
"eventdata": {
"broadcasterid": "casterID",
"broadcastername": "aCaster",
"gifterid": "",
"giftername": "",
"isgift": false,
"planname": "Some Subscription ($4.99)",
"tier": "1000",
"userid": "someID",
"username": "someName"
},
"eventtimestamp": "2020-10-16T17:33:46Z",
"event_type": "subscriptions.subscribe",
"id": "1iyAnn4NpVMZ9jYv0HDOQP4SfpS",
"version": "1.0"
}
]
}But it doesn't include information about if it was a 1/3/6/12 whatever subscription or not.
Please extend the payload (for both webhooks and the API) to contain this information about if it's a multimonth purchase
5 votes -
Initiate Redemption from the API Add the ability to trigger a reward redemption from the API - similar/same to what happens when clicking the reward in the chat dialog.
For example an extension has added a custom reward XYZ and to trigger a certain action in or for the extension this reward needs to be used.
So instead of the extension telling the viewer "please redeem reward XYZ to do this or that" and then waiting for the redemption, immediately trigger the redemtion via the API - saving the viewer the need to browse and look for the redemtion in question.
Result of this API…
3 votes -
Video Tutorial I am confused about this site. Please provide a video and explain more.
1 vote -
Watchparty status API/webhook/pubsub Please provide an API that provides
- what program is being watched
- What season/episode it is
- Episode/program title
- Cast information
- When started
- Link to the program on amazon (it's ASIN/whatever)
Information should be provide by
broadcaster_idfilter as a API
Sent out as a webhook (watchparty started, watchparty ended)
Provided as a PubSub event (started/ended/progress events?)PubSub and webhook should also provide information about a Watch party about to start
The watch party player does a countdown to show start, so that should be replicatable.
People whom are not amazon prime members, or do not have that program available to them…
6 votes -
Extend videos API to allow editors (and above) to automate downloads In a similar fashion as
The Videos API should be extended to provide the (original) VOD to authenticated users where that user is an Editor or better of the channel.
As in unmuted.
For the purpose of backing up/taking a copy of the Twitch stream and/or taking that content (that the streamer owns) for use on other platforms.
Editors can already do this via the Video Dashboard, so the API should support this also
41 votes -
'Get User Follows' endpoint response data should include 'logo' & 'notifications' The new API endpoint 'Get User Follows'
https://dev.twitch.tv/docs/v5/reference/users#get-user-followsCould include more data than what is currently provided.
The legacy endpoint alternative offers a lot more but not all of this info is required by default.
https://dev.twitch.tv/docs/api/reference#get-users-followsMy suggestion would be to at least provide the 'notifications' as well as the 'logo' info. To keep the requests at an optimal size by default, extra request parameters can be given such as:
?showLogo=true&showNotifications=true
(which can default to false when not present)or
?verbose=true
(which will provide an equivalent response to the legacy variant)The new endpoint should also only show this extra…
9 votes -
Twitch Test Environment Allow developers to mock responses from all common integration points- subs, bits, follows, streams, etc, and allow users to mock users as well.
This is useful for automated testing as well as building extensions.
5 votes -
Dashboard Activity Feed API Please provide access to the dashboard activity feed
- PubSub and Webhooks for real time
- GET API to obtain the history/missed events
14 votes -
Fetching a token returns `bearer` but Helix doesn't accept `bearer` Brief description
https://dev.twitch.tv/docs/authentication/getting-tokens-oauth
When you get a token, it returns token_type as bearer
If you take this value as is and call helix endpoints it doesn't work as helix only accepts Bearer
How to reproduce
Generate a token
Construct a header using the returned data by concatenating elements from the returned JSON
`Authorization: ' . tokentype . ' ' . accesstokenCall a helix endpoint
Get a 401
Expected behaviorTwitch accepts Bearer and bearer as valid
or
returns Bearer as the token type when fetching a token.
Additional context or questions
I'm not sure what the correct…
10 votes -
Create Custom Reward: Set Description on create When creating a custom reward it would be nice if we can set a description. Not all rewards can be easily described by the name.
1 vote -
Provide way to download Channel Analytics CSV Export I would like a way to programatically download the data that is in the Channel Analytics "Export Data" CSV.
3 votes -
Add verified and known bot information to Helix API Currently the only way to fetch this information is via a semi-undocumented endpoint. Given Twitch's past record on these endpoints, I don't want to rely on them as by my experience they have a tendency to suddenly disappear. For this reason, I'm asking for this information to be added to the Helix API.
7 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
- Don't see your idea?