PLEXICHATNarrative Docs
OAuth Scopes
Guides, route-group overviews, and live schema entry points for the Plexichat backend.
REST http://api.plexichat.com/api/v1Gateway ws://api.plexichat.com/gatewayVersion a.1.0-49
OAuth Scopes
OAuth scopes define which user data or application capabilities an external client is requesting during authorization.
Runtime Summary
| Metric | Value |
|---|---|
| Total scopes | 10 |
| Privileged scopes | 2 |
| Bot-required scopes | 1 |
Scope Catalog
| Scope | Privileged | Bot required | Description |
|---|---|---|---|
applications.commands | No | No | Create commands in servers you manage |
applications.commands.update | No | No | Update application commands |
bot | No | Yes | Add a bot to a server |
email | No | No | Access your email address |
guilds | No | No | Know what servers you are in |
guilds.join | No | No | Join servers on your behalf |
guilds.members.read | Yes | No | Read your member info in servers |
identify | No | No | Access your username, avatar, and banner |
messages.read | Yes | No | Read your messages |
webhook.incoming | No | No | Create webhooks in channels you manage |
Usage Notes
- request the smallest scope set needed for the integration
- privileged scopes usually deserve extra review because they expose more sensitive data
- the
botscope is special because it changes the authorization flow toward bot installation behavior - scope validation still happens server-side even if a client renders this list correctly