This permission extends to updating custom rewards themselves, so any rewards created through the UI will not be manageable by a client id with the channel:manage:redemptions scope granted. This makes no sense to me and makes instrumenting custom reward API requests a pain. What's the point of going through authorizing an app access code with the manage redemptions scope if it won't actually get that permission?
This permission extends to updating custom rewards themselves, so any rewards created through the UI will not be manageable by a client id with the channel:manage:redemptions scope granted. This makes no sense to me and makes instrumenting custom reward API requests a pain. What's the point of going through authorizing an app access code with the manage redemptions scope if it won't actually get that permission?