Channel points are the easiest way to let viewers take part in your stream: request a song, skip a video, ask a question. It gets interesting once a bot is supposed to react to a redemption. Then a few settings decide whether it sees the redemption at all and whether it can give points back.
What a custom reward is
Besides Twitch’s built-in rewards you can create your own. This is only available to affiliates and partners. Twitch allows up to 50 custom rewards per channel, active and disabled ones combined. Every reward costs at least one point and can carry a prompt for viewers of up to 200 characters.
Whether you create the reward in the creator dashboard or let a program create it through the Twitch API makes no difference to viewers. For bots it makes a big one; more on that below.
The settings that matter
Labels in the dashboard can change. The Twitch API names the settings like this, and that is where they are described authoritatively:
| API field | Effect | When it makes sense |
|---|---|---|
is_user_input_required | The viewer has to enter text when redeeming. | Requests, questions, anything a bot should evaluate. |
max_per_stream | Maximum number of redemptions per stream, for everyone combined. | Expensive actions that would otherwise flood the stream. |
max_per_user_per_stream | Maximum per viewer and stream. | So that one person cannot take every slot. |
global_cooldown_seconds | Cooldown between two redemptions; only applies when the cooldown is enabled. | Anything that visibly happens on stream. |
should_redemptions_skip_request_queue | The redemption counts as fulfilled immediately and skips the queue. | Only if nobody ever needs to follow up. |
How a bot notices a redemption
There are two ways. The official one is EventSub: a program subscribes to the channel.channel_points_custom_reward_redemption.add event and is notified of every redemption. It needs the channel:read:redemptions permission from you. The subscription can be limited to one specific reward.
The second way is chat. When someone redeems a reward with text input, the text appears as a chat message tagged with the reward’s ID. A chat bot can use that to tell which reward was meant. That is how our own bot works. What we observed in operation: rewards without text input do not show up in chat at all. Twitch does not officially document the ID in chat; only rely on it if your tool explicitly says it works that way.
Rule of thumb: if a bot should react to a reward, turn on text input. Then it works with EventSub bots and with chat bots.
The client ID trap: who may manage a reward?
This is the most common misunderstanding. Any app with the right permission may read all rewards. But only the app that created a reward may manage it. The Twitch API checks the client ID for this: updating, deleting, fetching redemptions and setting a redemption’s status only work with the same client ID that created the reward. Otherwise Twitch answers with a 403 error.
Rewards you created by hand in the dashboard belong to no app. No bot can change their status or edit them for you. It can only see that someone redeemed them.
Queue and refunds
Without “skip queue”, every redemption lands in your queue with the status UNFULFILLED. There you can mark it as fulfilled or reject it. According to Twitch, rejecting it (CANCELED) refunds the viewer’s points. With “skip queue” the redemption counts as fulfilled immediately, and a refund is no longer intended.
An automatic refund by a bot, for example when a request cannot be fulfilled, requires both: the reward was created by exactly this app, and the app has the channel:manage:redemptions permission. If either is missing, your queue is the only way.
What we learned in operation
- One reward, one job. If you use the same reward for two features, the tool decides which one wins. With us, “skip video” wins over a request. Create two rewards instead.
- Expect duplicate delivery. The same redemption can arrive twice. Our plugin discards a second skip redemption within five seconds.
- New reward, new list. Some tools only load the list of your rewards when you connect to Twitch. A reward created later is then missing from the selection until you reconnect.
- Connect with the right account. Twitch does not ask which account you mean when you connect. If your browser is logged in to a different channel, that is the one you connect.
How viewers skip a video or request a specific one with channel points in a 24/7 stream is described on the OBS plugin page.
Checklist
- Affiliate or partner, and still below 50 custom rewards?
- Text input enabled if a bot should evaluate the reward?
- Limits per stream, per viewer or a cooldown set?
- Skip queue only if a refund will never be needed?
- Should a bot refund points: did it create the reward itself?
- Reloaded the list in your tool after creating a new reward?