> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/discord.md).

# Discord

## OAuth app properties

| Property                | Value                                                                                                                                                                                                                               |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Yes.** With **Public Bot** on, an admin of any Discord server can add the bot and connect an account.                                                                                                                             |
| **Vendor review**       | **Required** past 100 servers: App Verification. Privileged intents (**Server Members Intent**) need a separate review once more than 10,000 unique users can see the app.                                                          |
| **Review time**         | Not published. After Discord's notice about privileged intents you have 90 days to apply.                                                                                                                                           |
| **Users before review** | 100 servers. Privileged intents work without review up to 10,000 unique users across those servers.                                                                                                                                 |
| **App owner**           | Any Discord account or developer team.                                                                                                                                                                                              |
| **Regions**             | One app works worldwide.                                                                                                                                                                                                            |
| **Client secret**       | No expiry documented. It can be reset on the **OAuth2** tab; the same goes for the bot token on the **Bot** tab.                                                                                                                    |
| **Rate limits**         | 50 requests per second per bot. The components call the API with the one bot token from the Backoffice, so all your users share this limit. 10,000 invalid requests (`401`, `403`, `429`) per 10 minutes lead to a temporary block. |
| **Checked**             | 2026-11-13                                                                                                                                                                                                                          |

**Limitations**

* An unverified app cannot be added to more than 100 servers.
* **List Guild Members** and the components built on it need the **Server Members Intent**. Above 10,000 users, Discord removes the intent if you do not apply for it within 90 days.
* A connected account is tied to the server picked during authorization. A user who works with several servers connects one account per server.
* After you reset the client secret or the bot token, update `clientSecret` or `botToken` in the Backoffice.

Sources: [Gateway intents](https://docs.discord.com/developers/events/gateway), [Privileged intent review](https://docs.discord.com/developers/gateway/getting-started-with-privileged-intent-review), [Change log](https://docs.discord.com/developers/change-log), [Rate limits](https://docs.discord.com/developers/topics/rate-limits), [Guild resource](https://docs.discord.com/developers/resources/guild). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Register OAuth2 app

Go to the Discord Developer Portal: <https://discord.com/developers/applications> and create a new Application.

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-de491ce503729b45c191b338eb93260e8dbe67f8%2Fdiscord-1.png?alt=media)

1. Click “New Application”
2. Give it a name, accept their **Terms of Service** and click “Create”
3. Open your new application

## Basic Information

To obtain your OAuth credentials, go to OAuth2 tab:

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-a05211011ec870401625a38d2967183d99acebeb%2Fdiscord-2.png?alt=media)

* Client ID: shown on the “Client information” card as “Client ID”
* Client Secret: click “Reset Secret” to generate a secret and copy it

You’ll paste these into the Appmixer Backoffice later.

## OAuth2 & Redirect URL

You must add the redirect/callback URL so Discord can return users to Appmixer after authorization.

* Go to OAuth2 tab
* In “Redirects”, add your Appmixer URL. Example:

  <https://api.YOUR\\_SUBDOMAIN.appmixer.cloud/auth/discord/callback>

Note: Replace YOUR\_SUBDOMAIN with your actual Appmixer subdomain. The path “/auth/discord/callback” follows the same pattern as other Appmixer connectors.

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-5f7bf08f67ec416fddbb0677ec4f3398d829bfa2%2Fdiscord-3.png?alt=media)

## Add a Bot and get the Bot Token

To make the events (sending messages, reacting to events) be from a bot, add one:

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-001a531a127d7c4ab0b2e9218f499efe62735dd8%2Fdiscord-4.png?alt=media)

* Click “Reset Token” to reveal the Bot Token and copy it

Keep the token secure. You’ll paste it in the Backoffice as well.

Check the settings below in **Authorization Flow**, recommended set up is:

* Public Bot: ON
* Requires OAuth2 Code Grant: ON
* Server Members Intent: ON

Rest can be turned off.

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-5cf9a5777334b1388bdf67b2f8bc331bfbfefa6d%2Fdiscord-5.png?alt=media)

## Scopes and Permissions

How you configure scopes:

* Installation → Default Install Settings:
  * User Install: applications.commands
  * Guild Install: applications.commands, bot

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-82b14d61315a34b79b1f5c52154dee8d126a351e%2Fdiscord-6.png?alt=media)

## Backoffice configuration

Configuration ID: `appmixer:discord` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-6bfa4baab708067906f78a47a7b44c393baf65ee%2Fdiscord-7.png?alt=media)

* `clientId` — Client ID from the **OAuth2** tab of the Discord app registered above. Not needed when Discord is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Client secret from the same tab. Not needed with the Auth Hub.
* `botToken` — Bot token from the **Bot** tab of the same app. Required: the components call the Discord API with this token, not with the user's token.
* `listChannelsCacheTTL` — Optional. How long, in milliseconds, the channel list of **ListChannels** used in the channel dropdowns is cached. Default `20000` (20 seconds).
* `outputFilePrefix` — Optional. File name prefix of the CSV file that **FindGuildMembers**, **ListChannelInvites**, **ListChannels**, **ListGuildEvents**, **ListGuildMembers**, **ListGuildMembersWithReactionsOnMessage** and **ListGuildRoles** create when their output is set to a file; the file is named `<prefix>-<component name>.csv`. Default `discord-objects-export`.

After saving, click **Connect account** on a Discord component in the Designer and complete the authorization.

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:discord -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>",
  "botToken": "<bot token>"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/discord.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
