Hi
I hope you are all doing good
I need some help. I am looking for a developer who can easily integrate twitch with my website https://cloptoncapital.com/. I tried a lot by myself but nothing happened. So if you have any information about it then please do let me know. Thank You

Currently, the only way for a bot to know its chat limits is by hard-coding them. Even using the (undocumented?) user chat info endpoint isn't sufficient to determine what hard-coded limits to apply today, since whisper limits depend on when an account was verified.

It would be much better for a bot to query a (documented) endpoint and retrieve its rate limits in that way.

Add Social links in response on endpoint "Get users"

inserire una funzione di chiamata all'api per ritornare la lista dei vip di un determinato canale per poi fare un login riservato ai vip, non trovo funzioni nell'api e questa cosa mi rallenta i lavori. [LINGUAGE ITALIAN]

The Kraken API for querying videos lists the available resolutions for archived broadcasts and current streams. The new API does not.

https://dev.twitch.tv/docs/api/reference#get-videos

So I'm trying to do a multi-room audio solution with Mopidy (https://mopidy.com/) and Snapcast (https://mjaggard.github.io/snapcast/), and I'm following many DJs on Twitch, and tune in for the music. I'd like to be able to have a Mopidy extension to be able to receive and listen to Twitch streams from the server, without having to use my phone or anything.

I don't mind if I need to login/OAuth token, I don't mind for the usual occasional audio ads, I just want to be able to access the AUDIO stream so I can listen to it more conveniently.

Could you add an endpoint equivalent for the Get User Emotes endpoint? my application uses the old one to show all the emotes a user can use but its not getting updated to support the new kinds of emotes being added to twitch.

The TZIDs in https://dev.twitch.tv/docs/api/reference/#get-channel-icalendar are currently prefixed by a / so they are /America/New_York for example. Removing the leading slash should vastly improve compatibility with iCal parsers (since the timezones are essentially IANA timezones then).

Given that EventSub only uses an App Access Token.

It's possible for a developer to obtain user authentication and never store the token (and/of refresh token if one exists (ie implict has no refresh)) and only utilise EventSub.

Please provide an endpoint

https://api.twitch.tv/helix/users/scopes

With a required parameter of:

id - a userID

That accepts ONLY An App Access Token

That returns

{
data: [
'array',
'of'
'scopes'
]
}

To allow developers to check what scopes a user has authorised the developer/ClientID to utilise

add follower emote to the list of emotes returned in the emote API

There are a lot of bots and some of them get gifted subs because they are just a "normal" user. anotherttvviewer, carbon14xyz etc. are all known bots and I think the developers of the bot should have the option to mark them as bots like in discord. It would be easier to understand for streamers, and they shouldn't get gifted subs.

I want my Twitch Extension to be able to copy text to clipboard. It seems as though that the iframe allowed permissions are limiting this. Therefore I request for Twitch staff to add clipboard-read; and maybe clipboard-write;

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.

The ability to interact with ban appeals with API would be a useful tools for developers who create full moderation/management suites for broadcasters. This could include the ban reason, the appeal reason. This would also help us fill the gaps with missing information that Twitch has right now, like tracking the number of appeals or storing the appeal reason after approved.

The ability to interact with ban appeals with API would be a useful tools for developers who create full moderation/management suites for broadcasters. This could include the ban reason, the appeal reason. This would also help us fill the gaps with missing information that Twitch has right now, like tracking the number of appeals or storing the appeal reason after approved.