Skip to content
Translate Ideas and Comments
Choose language:
There was an error during translation
← Developers

How can we improve the developer experience on Twitch?

Developers: API

Categories

Toggle Raid-ability of my channel (and minimum-amount threshold) through API

I utilize the API endpoints to disable a few things while wrapping up my stream (such as disabling commands, channel point rewards, change chat modes, etc). Within this workflow, I recently realized it would be super helpful to be able to disable or configure the raid-ability status of my channel as well. It would also be helpful to be able to control the other parameters, such as the min/max amount of viewers in a raid, account age, etc. It would all be amazing to be able to control through the API in the event of a wrapup, raid abuse, etc.

I think it's safe to say nearly every bot existing nowadays could easily incorporate this into their services, and in general I think it would provide a level of immediate control without having to use the already existing toggle within the creator dashboard. I can understand how this may seem silly since there already /is/ an option on the dashboard, but the same could be said about redeems, which can also be enabled/disabled via the dashboard and also have API endpoints to create/configure/delete them.

For example, say I get two or three 1-person goofy/troll raids back to back. At this point it would be super helpful to have an API endpoint that I could quickly pass a request to for temporarily disabling raids to my channel, OR increasing the threshold via this API endpoint. Then my bot could immediately detect repeated 1-person raids, and increase the threshold, or turn off raiding entirely for like 30 minutes.

And during a wrapup, when a streamer is usually DONE FOR SURE, the streamer could have a streamdeck button which runs the API request, or a bot that auto-shuts-off raids or maybe uses a !noraid command or something of that sort to trigger the same functionality.

In summary, an API endpoint to configure Raid-ability settings or outright shut off raids would be fantastic!
7 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Setolyx shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • NeighborhoodofMusic commented  ·   ·  Report

    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.
  • Gre_Gor commented  ·   ·  Report

    It would also enable something like Stream Deck to have a button for it.
  • UncleWooly commented  ·   ·  Report

    Very much agree! For those that play certain games or have a sensitive stream moment that they don't want interrupted temporarily, this would be really nice!