202 results found
-
Endpoints to approve/deny messages held for review by AutoMod Messages held by AutoMod for review can be received through the documented
chat_moderator_actions
PubSub topic, however the New Twitch API does not appear to offer a way for moderators to approve/deny these messages, which would be useful for bots or moderators that use third-party tools to further customize their moderation experience.5 votesWe added the Manage Held AutoMod Messages endpoint in May.
-
broken example example doesn't work "error":"Unauthorized","status":401,"message":"OAuth token is missing"}curl: (3) URL using bad/illegal format or missing URL
2 votes -
1 vote
-
dimensionn There's a typo under mobile guidelines:
"dimensionn"1 vote -
Bans: who did the action Hydrate the bans topic to include the user_id, login of the user that performed the ban action
So add
moderator_user_id
moderator_user_login
moderator_user_name
to the event
9 votes -
Expose VOD seek events I'd like to be able to know when a user seeks in a VOD that is embedded on my site. Ideally the event would contain the before/after timestamps so I can know the delta. Thanks!
1 vote -
Chatters / Viewers Helix API Endpoint The existing API endpoint for getting chatters predates User IDs and only returns usernames. It's also part of TMI and not officially documented, which could result in it being removed at any point without any notice.
Many bots use the endpoint for channel loyalty points, and then have to make secondary calls to the get the user ID.
220 votesThe "Get Chatters" endpoint is now in general availability (as opposed to open beta). "user_id" and "user_name" have been added to the response. Documentation can be found here: https://dev.twitch.tv/docs/api/reference#get-chatters
-
Channel Points API multiple suggestions/requests A great many Ideas/notes and stuff from the Developer discord was collected and thrown into a Google Docs
https://docs.google.com/document/d/1dxx04pp6VVqY9s9JRcVP3w9keBHrRR5LB3Q043McS1Q/edit?usp=sharing
Covers
- CRUD store items
- Fetching/updating points values
- handling store redepmtions
- Stuff about webhooks
- Stuff about points in extensions (see also https://twitch.uservoice.com/forums/310213-developers/suggestions/38874571-channel-point-transaction-in-extension )Throwing it here so it's here as well as already sent to Twitch via Dev Advocacy
102 votesAs announced at last week’s Developer Day, we now have set of Channel Points endpoints and EventSub subscription types. This initial release may address much of the feedback captured here, if you still have features you would like so see, please feel free to file more UserVoice ideas under the “API” category.
-
Polls API Please provide an API to CRUD polls and observe the results in real time when a poll is ran.
Ability to read historical/past polls would also be nice
199 votes -
Add channels.raid Webhook Type Trigger: Triggers whenever a broadcaster hosts on a broadcaster's channel.
Motivation: We get this information from the IRC. Such an event in the EventSub would save us an continuous IRC connection in the chat. Therefore we only need to rely on webhooks.
16 votesChannel Raid is now available. See the EventSub subscriptions page for more information: https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types
-
Allow access to the "Get Channel Chat Badges" endpoint using an App Access Token All of the new emote and badge endpoints can be accessed using an App Access Token except for /chat/badges which needs a User OAuth Token.
I don't see why this endpoint needs a user token since the badges can be viewed publicly on the subs page and It doesn't reveal any private info about a user.3 votesThank you for reporting this issue. This endpoint now supports access with an App Access Token.
-
Fixing an error There's an error in Section "Using cURL to get the information".
curl command needs param -X if you want to specify the method, for example GET in this case:
curl -X GET "<url>"...1 vote -
Add Display names to live reactionary chat data Any topic, that deals with reactionary events from chat such as cheers or subscriptions (new/resub/etc.) it would be beneficial to have a display name for all parties involved, the user who subbed, cheered, but also gifted, and broadcaster.
Reasoning:
- Various names have a certain capitalization that identifies that user. Without that there are cases that make the name very difficult to decipher for the viewer if the name appears on screen, due to all the letters being lower case or upper case.
- If the name was already displayed in chat, then this data should also propagate to the…10 votes -
Emotes by channelID It is impossible to get the emotes for a channel from the API via Channel ID
The API uses "emotesetID" and there is no API endpoint that provides the emotesetID for a given channel
Please provide a way to get the emotes for a channel via ChannelID/ChannelLogin
116 votesGet Channel Emotes, Get Global Emotes, and Get Emotes Sets are now available in the API. https://discuss.dev.twitch.tv/t/announcing-api-endpoints-for-twitch-emotes/32073
-
Bans topic sends for timeouts and bans but doesn't differentiate The bans topic will send an event for someone getting banned or timed'out from the channel.
The bans topic doesn't tell you if it was a ban or a timeout.
- Timeout's either need to be a seperate topic (not preferred)
- The payload extended to include a time parameter, so timeouts can be differetiance (preferred)
(Webhooks have the same problem ironically)
6 votes -
Provide Hype Train Begin level This is more of a uncertainty of necessity, as the hype train documentation is still fairly new to me. As a broadcaster there have been scenarios where a level 5 hype train was the starting level.
Providing the level at the start could alleviate some confusion for progress and end as well as provide some consistency for the other two event types.
Reasoning:
The hype train on the end user side could start at a completed level 5. Depending on when the event is actually sent, this could provide odd results.Related events:
- channel.hype_train.begin
- channel.hype_train.progress
- channel.hype_train.end11 votes -
Create Sandbox/Testing Environment for API Twitch currently completely lacks any sort of API testing feature. This causes extreme difficulty for debugging code made with the Twitch API.
This is unacceptable when the vast, vast majority of websites/software that have a public API have some sort of testing feature that sends tests through the same API endpoints as production.
For example, a piece of software I was working on recently worked great, but it turned out that events for subscriptions was broken. We have absolutely no way to test subscription events through the Twitch Pub/Sub API besides actually buying subs. I didn't actually fix it until…
9 votesTesting Affiliate/Partner events is now possible with the Twitch CLI. See comments for more details.
-
missing scopes Scope list says it's comprehensive, but it does not include user:read:email which is listed in some other docs.
1 vote -
Typo in extension.bits_transaction.create text The section title under the payload section of the
extension.bits_transaction.create
event is "Channel Hype Train End Notification Example" when it should read "Extension Bits Transaction Notification Example"1 vote -
API for channel banned terms CRUD https://dashboard.twitch.tv/u/USERNAME/settings/moderation/blocked-terms
There is no API for automation of adding/removing/listing a given channels blocked-terms
When adding/removing a term modlogs display in chat as
barrycarlyon used: /addblockedterm THISISATEST.
barrycarlyon used: /deleteblockedterm THISISATEST.But these are not valid chat commands either.
Please provide an API to CRUD channel blocked terms
83 votesWe released the Get, Add, and Remove Block Terms endpoints last November.
- Don't see your idea?