Add scheduled-events endpoint scope for OAuth2

[Inrixia]

So currently the https://discord.com/api/v10/guilds/{guild.id}/scheduled-events endpoint can only be accessed via a bot that has been added to a guild with permissions and is not accessible with a client token from OAuth2.

I wanted to have a client app access this endpoint, currently I would have to sign in the client using OAuth2, fetch their guilds, request to the applications bot (via a separate api that has the bots secret) to get the guilds events, if the bot is not in the guild then respond prompting the user to add the bot (and hope the user has permission to do so), and then fetch the events.

This seems overly complex for just wanting to fetch the events for guilds a user is in when it should be possible to just have it as a scope granted allowing for the client to call the endpoint directly without the need to add a bot to the server.

[kingmigdor]

That would not make guild events private once a member authorizes with some kind of scope of that. It would mean that the bot needs to be on every server, which does not equal to what the guilds scope returns.
I would rather think that it would be cool to make a scope that returns the events a user subscribed to. That would not fix it 100% but that's the best thing I could expect to happen on a users behalf.

[Inrixia]

I was assuming that a client calling the endpoint would not be able to do so with guild id's that client is not a part of meaning events would still be private as per what a user can see normally.

Having a scope for events a user is subscribed to would also work though would not allow seeing other events that they haven't subbed to in guilds they are in so ideally this would just be a parameter or handled by user code.

[IllagerCaptain]

I was assuming that a client calling the endpoint would not be able to do so with guild id's that client is not a part of meaning events would still be private as per what a user can see normally.

Having a scope for events a user is subscribed to would also work though would not allow seeing other events that they haven't subbed to in guilds they are in so ideally this would just be a parameter or handled by user code.

GitHub has "sub-scopes" (repo, repo:status, etc) so to say, so Discord could probably do something similar for this case, a scope for all events and a scope for subbed events. For example, guilds.events.read for all and guilds.events.read:subscribed for subbed. Or if they wish to use the same system I guess guilds.events.readall and guilds.events.readsubcribed would work.