API Token required scope not always correct in API

Nice to know, you also need settings.read to execute… Maybe this should be updated (-;

Thanks @joep, @henri

Thank you for the feedback @henk_stobbe: I just tested it out as well and confirmed the request returns “Access denied” when using settings.write as scope rather than settings.write & settings.read combined and linked to the same Access Token.

I will report it internally and ask to change it