Channel Point API is too restrictive

Then how do you expect the very same streamers to create code to process channel point rewards?

You just answered your own problem with the same problem.

The documentation clearly states

Returns a list of Custom Reward objects for the Custom Rewards on a channel. Developers only have access to update and delete rewards that the same/calling client_id created.

and

Returns Custom Reward Redemption objects for a Custom Reward on a channel that was created by the same client_id .

Developers only have access to get and update redemptions for the rewards they created.

So if you the streamer are reading the docs for getting/updating a Reward. Then it should be clear that you need to create it via the API also.

Sure that is what many of us sit on the forums of Dev Discord to help with

We spent a great many time dealing with the oAuth requirements of Helix when that was introduced, this will just be the same thing for us third party devs that take the time to help others.

Now in the example of an extension.

The moment you install the extension, you’ll get sent/suggested to go to the config view to configure the extension.

The config view will then prompt for authorization to read/write channel points.

The extension will then auto create the channel point rewards it needs

The extension will then tell the user in the config view they can use the “normal” channel points dashboard to modify the reward, such as pricing or images for that reward. (or yeah have a customized widget in the config view to modify pricing since the API doesn’t let us set images)

So it’s all “one click” for the example of an extension.

The same extension can then auto turn off the channel point rewards if the “game”/whatever for that extension is disabled.

1 Like