Obtain a user access token with the channel:manage:redemptions scope for the broadcaster account
POST to https://api.twitch.tv/helix/channel_points/custom_rewards with a JSON body containing title, cost in channel points, and optional fields like prompt, is_user_input_required, and max_per_stream
Capture the returned reward ID; the channel can have a maximum of 50 custom rewards (enabled and disabled combined)
Subscribe to the channel.channel_points_custom_reward_redemption.add EventSub event to receive real-time webhook or WebSocket notifications when a viewer redeems the reward
After fulfilling the redemption in your backend, PATCH https://api.twitch.tv/helix/channel_points/custom_rewards/redemptions to set the redemption status to FULFILLED or CANCELED
Known gotchas
Only the broadcaster's own user access token can create rewards; app access tokens and moderator tokens are rejected for this endpoint
Channel points redemptions via EventSub replace the legacy PubSub topic that was removed in April 2025 — do not attempt to use PubSub for redemption events
The 50-reward cap counts disabled rewards; if a broadcaster is at the cap you must delete an existing reward before creating a new one
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp