Current problem
To my knowledge, a user cannot add a webhook to a guild (for which they have permissions) from a third-party service (such as a website).
Using
scope=webhook.incoming displays the message “webhook.incoming is not a supported scope.”Proposed change
Implement the
webhook.incoming scope for the /oauth2/authorize endpoint as it exists on Discord, which allows the user to select a guild and then a channel to which to add the webhook, before returning the details of the created webhook to the service that initiated the request.Platform
API
Additional information
Current flow for Discord webhook:
- The user goes to
https://discord.com/oauth2/authorize?response_type=code&client_id={client_id}&scope=webhook.incoming&redirect_uri={redirect_uri} - The user selects the guild, then the channel where they want to add the webhook. (Discord webhook.incoming example.png)
- The browser redirects to the redirect_uri with the
code, which can then be used to retrieve the information for the created webhook (token, URL, name, guild_id, ...).