435 results found
-
Missing information Okay, I got the user access tokens... not how to use it? The page ends without a word...
(like how to get what user is the one who accepted the request).
Also the scope list is not full - Discord use other roles as well, not mentioned in that docs.2 votes -
Add query parameter option to make non-interactive frames more visually clean I have embedded my Twitch channel on my website as a non-interactive iframe in my side panel.
Example:
https://imgur.com/a/v1wc8riHowever, there is so much text there which clutters the UI.
By having my stream title there from when I was online does not add any value. It certainly does not promote my channel.
I would much more prefer if I could just have the bare minimum there and I can show my own offline-image.
Example:
https://imgur.com/a/v1wc8riIt would be nice if we had a new query parameter option for embedding channels, which could remove any promotion texts or videos /…
6 votes -
Stream schedule API - show segment timezone https://dev.twitch.tv/docs/api/reference/#get-channel-stream-schedule
Creating schedule segments uses IANA timezone names, but there's no way to see the specified timezone when the schedule is viewed.
1 vote -
Get Editors by userid Add optional parameter for "user_id" as many of the other endpoints.
1 vote -
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 -
Add PKCE Support to the OAuth2.0 Authorization Code Flow I am currently developing a native Android application for Twitch and want to make use of the OAuth2.0 API. Since the Twitch Authorization Server doesn't seem to support the PKCE (Proof Key for Code Exchange), i will have to put my client secret into my native application, which isn't secure at all, because the app can easily be decompiled.
This is a requirement for all native apps, as stated by the IETF in RFC 7636 (https://tools.ietf.org/html/rfc7636).
I hope to see this implemented soon, because this poses a huge security risk for all native apps and their developers.
48 votes -
Implicit Code Flow Samples First of all, thank you for providing developers with valuable tools and apis for twitch. I greatly appreciate the code samples that were provided, however I noticed that there was only a code sample for the authorization code flow. I feel that developers would greatly benefit from examples of how best to work with the implicit code flow. I know this has been an issue for me. For example, if you create an electron application with a modern javascript framework that manages routing, the redirect part of code flow becomes a sticking point. Most of them will use localhost for…
2 votes -
no Vip Label but it's great It was very useful for my little game but I would have liked a vip tag.
Except that it has served me perfectly. Thank you very much.1 vote -
'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 -
Moderator Actions PubSub topic should work for all moderators of the channel The
chat_moderator_actions
topic in the PubSub documentation appears to only work with a broadcaster OAuth token. This prevents third-party modding tools that don't use some kind of centralized system from accessing information that is vital for effective modding (such as which mod performed an action, actions that aren't otherwise visible like unbans and viewing and approving messages filtered by AutoMod).With a centralized system the broadcaster could provide a token somehow that the moderators don't need to have access to directly, however with purely clientside tools this is not feasible. I'm also not sure why moderators should not have access…
52 votes -
Add bet support to API (For Streamer AND Viewer) CRUD for bet as streamer
CRUD for bet as viewerAs streamer:
- Being able to start/cancel a bet from endpoint
- Being able to state who won from endpoint
- Maybe get stats about the bet (invested coins, status, nb of participant, ...) (as Events or/and as HTTP API)
As viewer:
- Receive an Event when there is a new bet
- Get bet info using endpoint (remaining time, title, bet A, bet B, nb of people who bet)
- Place a bet using endpoint
- Event win or lose4 votes -
Extend Start commercial to include preroll data When streamers run ads, they'd like to know how long the PreRolls are disabled for.
Please extend https://dev.twitch.tv/docs/api/reference#start-commercial to return preroll data
For example
{
"data": [{
"length" : 60,
"message" : "",
"retry_after" : 480
}]
}becomes
{
"data": [{
"length" : 60,
"message" : "",
"retryafter" : 480,
"prerollends": unixTimestamp
}]
}13 votes -
Authentication Docs Improvement Honestly this whole documentation is a bit sloppy. There should be clearer examples of using the APIs as I had to go Googling how the authentication actually works as the headers seem to be different than this suggests.
4 votes -
API to manage Channel Sub badges/sub flair badges Similar to
https://twitch.uservoice.com/forums/310213-developers/suggestions/41137957-upload-emotes
But for sub badges and the flair for t2/t3
5 votes -
Bulk data fetch for Get Subscriptions, Follows, Blocks etc. The current APIs max out at 100 items per page, and while this is fine for most channels, there are some where you end up having to paginate for a long time to reach the end of the list.
Given there is rate limiting in place, would it be possible to make an endpoint (or use the current endpoints and add an "all" query parameter) with a high rate-limit cost that allows for the bulk fetching of this information?
1 vote -
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 -
bad Where is all the information regarding --header 'Authorization
1 vote -
Extend heix subscribers or provide another endpoint for Lifetime Subscriber data This guide descibes how Partners can assign someone a lifetime sub that doesn't count to rev of points
https://help.twitch.tv/s/article/lifetime-subscriber-guide-for-partners
The API doesn't present any information as to who is a lifetime sub or not.
So we cannot guestimate sub points (or revenue if we are building revenue reporting tools for streamers we work with) from the API as we don't know who is a lifetime sub or not.Please provide an API endpoint that lists these subs, which would be "cheaper" than a boolean flag added to the subscribers endpoint
3 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 -
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?