961 results found
-
Publish Official Typescript Typing's for all Data Models It would be very easy to build and design for if there were official typing for all data endpoints. The data between all the different API's for the same data isn't consistent, and with event sub, since it no longer relies on the underlying Helix endpoint, that data can now be different too. This will also mitigate typos on the docs which causes huge headaches when trying to code for API responses and the data not working, or missing fields. The typing can specify which fields are required and which are optional, so when designing your app, you can easily…
3 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.
-
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 -
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 -
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 -
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 -
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 -
Get Custom Reward Redemptions "missing redemption status" Declares that only broadcasterid and rewardid are required.
A call to
results in
{
"error": "Bad Request",
"status": 400,
"message": "missing redemption status"
}The documentation lists status as not required
3 votes -
It's impossible to control the "core" rewards Topic.
Cannot control highlight message/unlock emote rewards to enable/disable/change price or even list them etc via this API
3 votes -
Provide uptime in channel information endpoint channel information endpoint provides "gameid", "gamename" and "title" for live streams, but it doesn't return the stream uptime as displayed below a live stream; would be useful to acquire this via API.
3 votes -
Inaccurate info in instrcutions It appears that the Glitch file has been changed! I couldn't get the !dice command to work, until i figured that the command had been changed to !d20 along with the number of sides changed to 20. Or maybe this was a ploy.... to help me understand coding better... Thanks!
3 votes -
3 votes
-
"Build your first Extension" section lacks critical information The "build your first extension" walkthrough was perfect until about the half-way mark, then it started omitting hugely important steps. I had to stumble around to try and keep up, and although I was modestly successful, I was not able to see my Panel extension in my channel. Would have been helpful to actually have a zip file of assets to upload, because I have no idea whether I did that step correctly.
3 votes -
Documentation is misleading The example and/or documentation of the "Channel Points Event Message" seem to be wrong/misleading, because the example reply does not match the structure of "Message Parameters: All Messages"
3 votes -
Modify Channel Information says "Query parameters" example post says JSON blob https://dev.twitch.tv/docs/api/reference#modify-channel-information
The example calls uses JSON, but the documentation talks about Query String/URL encoded form.
Docs should cover both possibilities and examples should cover both methods
3 votes -
Embed documentation doesn't mention the SSL requirment https://dev.twitch.tv/docs/embed/ and it's child pages mention the requirements for parent but never SSL
3 votes -
Unify data that is returned by various API endpoints concerning channels Specifically talking about:
- Get Channel Information: helix/channels
- Search Channel: helix/search/channels
- Get Users: helix/usersThose endpoints all return data concerning a specific channel, but all of the JSON responses are different and no single endpoint contains all the data you need.
Say I have a user id and want to get the profile picture of that channel, whether it is live and the title of the broadcast.
For the profile picture I have to hit the 'Get Users' endpoint.
For the 'isLive' info I need to hit the 'Search Channels' endpoint, and then find the correct user from…3 votes -
Chat Extension Type I would like to develop extensions to the chat box directly, that can fundamentally alter how it functions.
3 votes -
Subscribe to category with wehbooks Currently you can subscribe to a webhook to receive a handful of types of events. The only way to see when a stream goes live is to subscribe to a topic for that particular user. It would be incredibly useful to specify a category and receive a webhook whenever a stream goes live in that category.
3 votes -
Add user profile image and basic game info on /helix/streams for /helix/streams can we add:
profileimageurl from /helix/users
and the game name (and potentially boxarturl) from /helix/gamesThis is very basic info related to the stream and would be really nice to have available in a single call rather than 3 separate calls. This is especially important with bots that are trying to get the status of many streams in a short period quickly racking up api calls
3 votes
- Don't see your idea?