979 results found
-
Allow filtering the JSON API response For example, the YouTube Data API has the "fields parameter" to accomplish this, an example being: items(userid,username,title)
https://developers.google.com/youtube/v3/getting-started#fields
Thanks!
3 votes -
Pull boxart from Giantbomb Boxart used on a category's Giantbomb page should be automatically set as the boxart on Twitch.
1 vote -
4 votes
-
5 votes
-
Add endpoints to set and retrieve moderator comments for a user See https://blog.twitch.tv/channel-moderation-tools-in-chat-4188af21dbf9 for details.
29 votes -
10 votes
-
How to link out on a mobile extension Twitch documentation does not state how to handle opening a new window on a mobile extension.
3 votes -
167 votes
-
13 votes
-
Add subscriber only status to Streams API endpoint. Right now there is no official way (there is an undocumented endpoint) to determine whether a stream is sub only or not. Subscriber only status prohibits a lot of people from interacting with the stream, so it'd make sense for applications to be aware of such a state.
25 votes -
Add the bits:read scope to bits enabled extensions I'm looking to add functionality to an extension where all bits count but bits within the extension have a weighting against those that aren't. I have my own bits transactions through the transactions endpoint but at the moment I have to ask for the scope separately. As my extension is already asking for the
channel:read:subscriptionsI thought it may be a good option to add this as an extra scope to ask for or possibly ask for within the same auth loop as the subscription read7 votes -
Allow pubsub whispers in Developer Rig The Twitch Developer Rig should support pubsub whispers. It current supports normal broadcasts, but not whispers to target a specific user's frontend.
2 votes -
2FA status in users endpoint (when authing as the user) We third party dev's often build tools that assist with moderation actions/services for broadcasters.
We tell Moderators to enable 2FA, but we have no way to check it.
It would be useful to block Logins to our tool if 2FA is not enabled. But 2FA data is not surfaced in the API and there's no way to require a User to be 2FA during the login/oAuth loop.
I'd like to see the users endpoint(s) provide 2FA status.
I expect this to be behind the user read or openID scopes.openID allows email verified. Why not 2fa status (for example)
Worth…
37 votes -
Include username in onAuth callback when a user has granted ID access. Some third-party developers request id access on their Extensions just for the purpose of getting a viewer's username to build a more personalized experience. The only way to do so is by relying on the Helix user endpoint on their EBS. The Helix team already modified any payload that has a user id to also deliver a username and save developers the extra step of using the /users endpoint, so it's natural for Extensions to follow that path.
9 votes -
Ordering by date of helix endpoints Being able to order some of the Helix endpoints by date would be useful
Follower for example would need in some cases 11k+ calls to the follower endpoint to just get the 100 followers who had followed for the longest time.
This would also be good in the subscription endpoint if cumulative and streak get put into the Helix API
10 votes -
9 votes
-
/helix/moderation/enforcements/status - Return error messages instead of generic 500s When user IDs in the provided data payload do not exists, the endpoint returns a 500 error. Ideally this should return a more detailed error code with an error message related to user IDs.
3 votes -
Add clear all button to Extension whitelists Some developers may need to cycle their Extension's whitelist with a big number of accounts. There's already an option to mass add users to a whitelist. So it's only natural to complement it with a mass delete.
1 vote -
Product SKU management in Monetization section of developer platform Currently the management of extension SKU's is only done via the Developer Rig.
Since the rig is an optional, many people are developing / testing without using it & the fact that its a development environment, its a strange place to place/manage production SKU's. These would be better managed from the platform itself under the Monetization tab of each Extension.
4 votes -
Streamer whitelist removal after extension is live - [Beta release] Currently, if you launch an extension with a streamer whitelist, there is no way to remove this whitelist once the extension is live.
I would like to suggest being able to remove (And only remove not add) the streamer whitelist once the extension is live. This will enable doing 'beta-releases', which is a very common rollout practice and has a lot of benefits for the developer.
In this way a developer can release an extension to a set group of streamers who want to participate in the beta test.
Once the developer has determined that things look good and it…
6 votes
- Don't see your idea?