Submitting this on behalf of Jeff Fritz, which he mentioned while talking about a Channel Points streaming opportunity. I was talking about building an example that uses webhooks to flag when a specific category is selected for a stream so a developer knows when to enable or disable a channel points reward. His question was why Twitch doesn't handle that automatically.

If there was an optional category property that could be set when creating the custom reward, Twitch could potentially handle enabling/disabling a reward more reliably if the context for switching is a category update, which would probably be the most common use case.

If enabling/disabling was based on something other than a category update, the developer can ignore the use of the category parameter, or use them in tandem. For example, focus on building logic to switch rewards for different parts of the game and not have to worry about also checking the active category.