Restriction when enabling/disabling rewards via API request

[BarryCarlyon]

@AraqueLars

So my guess It’s that, via API, one app can only modidfy the rewards created previously by the app itself (using the create entry point). And this is a safety measure since, hypothetically, I could grant permissions to N different apps, and all of them could create new rewards. And if all those apps could edit the rewards from everyone else, it would be a bit of chaos. Right?

Correct.

@AraqueLars

But my point is, if my app is linked to my twitch user, and that app makes a server request to edit a reward (created by me using the web dashboard), shouldn’t the system be able to recognize that the app is actually me and then allow the edit??

No as thats not what the scope granted access to

The scope (manage channel rewards) on the API only lets you manage rewards that the ClientID created.

The dashboard ClientID != the ClientID you used

And the “owner” of the ClientID is irrelevant (as thats not how oAuth works)
There are not “permissions” between a ClientID and the owner of the ClientID