Settings and activity
3 results found
-
7 votes
An error occurred while saving the comment 
NeighborhoodofMusic
supported this idea
·
-
2 votesNeighborhoodofMusic
shared this idea
·
-
3 votesNeighborhoodofMusic
supported this idea
·
The Problem:
Currently, broadcasters have no way to programmatically toggle their "Incoming Raid" settings (such as allowing/denying all incoming raids or adjusting viewer limitations). The only way to change these settings is manually through the Creator Dashboard on a web browser or via the Twitch Mobile App's Quick Actions.
This creates a massive friction point for broadcasters who need to manage their stream's atmosphere on the fly. Whether it is an IRL streamer trying to wrap up their broadcast while away from a keyboard, or a gamer deeply immersed in a critical moment, having these settings locked behind a web dashboard prevents creators from protecting their channel's pacing and vibe.
The Solution:
Please expose the Incoming Raid settings to the Twitch API so that third-party applications can read and update a channel's raid preferences dynamically.
The Use Case & Integrations:
If this endpoint existed, streamers could seamlessly integrate raid defenses into their existing automated workflows using tools like Streamer.bot, Mix It Up, and Elgato Stream Deck.
Examples of how this would be used:
The Story-Driven Gamer: When a streamer is playing a narrative-heavy RPG and reaches a highly emotional or pivotal cinematic cutscene, the last thing they want is a massive raid and the accompanying alerts ruining the moment. With an API endpoint, a streamer could hit a "Cinematic Mode" button on their Stream Deck that dims their lights, hides their overlay, and temporarily disables incoming raids until the scene is over.
The IRL Streamer: An IRL streamer walking around outside could type a simple chat command like !noraids into their phone. Their chat bot would catch the command and hit the API to instantly deny incoming raids, allowing them to sign off peacefully without needing to fumble through the mobile dashboard.
The "Outro" Button: A desktop streamer could map a multi-action button on their Stream Deck for "Ending Stream." Pressing this button would swap their OBS scene to the "Ending Soon" screen, play their outro music, and ping the API to disable incoming raids so they can prepare their own outgoing raid without an awkward collision.
Proposed API Functionality:
Ideally, we need a PATCH endpoint (e.g., PATCH [https://api.twitch.tv/helix/raids/settings](https://api.twitch.tv/helix/raids/settings)) that requires a user access token with a specific moderator/broadcaster scope.
The endpoint should accept a JSON body allowing us to update:
allow_incoming_raids (Boolean - True/False)
minimum_viewer_count (Integer)
maximum_viewer_count (Integer)
By giving developers access to this specific setting, you will empower streamers to better control their channel's pacing, prevent awkward raid collisions, and preserve the immersion of their content.