Application object
Application structure
ID of the app
Name of the app
Description of the app
List of RPC origin URLs, if RPC is enabled
When
false, only the app owner can add the app to guildsWhen
true, the app’s bot will only join upon completion of the full OAuth2 code grant flowPartial user object for the bot user associated with the app
URL of the app’s Terms of Service
URL of the app’s Privacy Policy
Partial user object for the owner of the app
Hex encoded key for verification in interactions and the GameSDK’s GetTicket
If the app belongs to a team, this will be a list of the members of that team
Guild associated with the app. For example, a developer support server.
Partial object of the associated guild
If this app is a game sold on Discord, this field will be the id of the “Game SKU” that is created, if exists
If this app is a game sold on Discord, this field will be the URL slug that links to the store page
App’s default rich presence invite cover image hash
Approximate count of guilds the app has been added to
Approximate count of users that have installed the app (authorized with
application.commands as a scope)Approximate count of users that have OAuth2 authorizations for the app
Array of redirect URIs for the app
Interactions endpoint URL for the app
Role connection verification URL for the app
Event webhooks URL for the app to receive webhook events
If webhook events are enabled for the app.
1 (default) means disabled, 2 means enabled, and 3 means disabled by DiscordList of webhook event types the app subscribes to
List of tags describing the content and functionality of the app. Max of 5 tags.
Settings for the app’s default in-app authorization link, if enabled
Default scopes and permissions for each supported installation context. Keys are application integration types, values are integration type configuration objects
Default custom authorization URL for the app, if enabled
Example application object
Application integration types
Where an app can be installed, also called its supported installation contexts.| Type | ID | Description |
|---|---|---|
GUILD_INSTALL | 0 | App is installable to servers |
USER_INSTALL | 1 | App is installable to users |
Application integration type configuration object
Install params for each installation context’s default in-app authorization link
Application event webhook status
Status indicating whether event webhooks are enabled or disabled for an application.| Name | Value | Description |
|---|---|---|
DISABLED | 1 | Webhook events are disabled by developer |
ENABLED | 2 | Webhook events are enabled by developer |
DISABLED_BY_DISCORD | 3 | Webhook events are disabled by Discord, usually due to inactivity |
Application flags
| Value | Name | Description |
|---|---|---|
1 << 6 | APPLICATION_AUTO_MODERATION_RULE_CREATE_BADGE | Indicates if an app uses the Auto Moderation API |
1 << 12 | GATEWAY_PRESENCE | Intent required for bots in 100 or more servers to receive presence_update events |
1 << 13 | GATEWAY_PRESENCE_LIMITED | Intent required for bots in under 100 servers to receive presence_update events, found on the Bot page in your app’s settings |
1 << 14 | GATEWAY_GUILD_MEMBERS | Intent required for bots in 100 or more servers to receive member-related events like guild_member_add |
1 << 15 | GATEWAY_GUILD_MEMBERS_LIMITED | Intent required for bots in under 100 servers to receive member-related events, found on the Bot page in your app’s settings |
1 << 16 | VERIFICATION_PENDING_GUILD_LIMIT | Indicates unusual growth of an app that prevents verification |
1 << 17 | EMBEDDED | Indicates if an app is embedded within the Discord client (currently unavailable publicly) |
1 << 18 | GATEWAY_MESSAGE_CONTENT | Intent required for bots in 100 or more servers to receive message content |
1 << 19 | GATEWAY_MESSAGE_CONTENT_LIMITED | Intent required for bots in under 100 servers to receive message content, found on the Bot page in your app’s settings |
1 << 23 | APPLICATION_COMMAND_BADGE | Indicates if an app has registered global application commands |
Install params object
Install params structure
Permissions to request for the bot role
Installation context
An app’s installation context defines how it’s installed: to a server, to a user, or both. The installation context affects how your app can be seen and used within Discord. For example, apps installed only to a user can’t take actions in a server, and apps installed only to a server can’t be accessed within a user’s DMs.Server context
Apps installed in a server context (server-installed apps) must be authorized by a server member with theMANAGE_GUILD permission. Server-installed apps are visible to all members of the server, but other factors (like command permissions) determine where and when specific members can interact with the app.
During installation, server-installed apps are authorized with a specific set of OAuth2 scopes and bot user permissions that determine what resources and data the app can access in that server.
User context
Apps installed in a user context (user-installed apps) are visible only to the authorizing user, and therefore don’t require any server-specific permissions. Apps that support the user installation context are visible across all of an authorizing user’s servers, DMs, and GDMs, but are forced to respect the user’s permissions in the surface where the app is being used.Setting supported installation contexts
By default, newly-created apps only support installation to guilds. You can update which installation contexts your app supports in your app’s settings. On the Installation page under the Installation Contexts section, you can select the installation contexts your app supports.If you update your app to support a new installation context, you will need to update your existing commands if you want them to be supported in the new context.
Install links
Install links provide an easy way for users to install your app in Discord. If you have an install link configured, an “Add App” button will appear in your app’s profile and App Directory page. There are three options when configuring an install link: “Discord Provided Link”, “Custom URL”, and “None”.Discord provided link
The default Discord Provided Link is a short link that guides users through the installation flow with your app’s configured installation contexts. Discord Provided Links don’t have scopes or bot user permissions defined in the URL. Instead, these links prompt the user for the scopes and bot user permissions configured in your Default Install Settings.Discord Provided Links are limited to the
application.commands and bot scopes.Custom URL
A Custom URL is an alternative to the Discord Provided Link that gives you more control of where users are directed when they click “Add App”. A Custom URL is commonly an OAuth2/authorize URL that has defined scopes, permissions, and an installation context (integration_type).
Get current application
GET
/applications/@meEdit current application
PATCH
/applications/@meAll parameters to this endpoint are optional.
JSON params
Default custom authorization URL for the app, if enabled
Description of the app
Role connection verification URL for the app
Settings for the app’s default in-app authorization link, if enabled
Default scopes and permissions for each supported installation context
App’s public flags. Only limited intent flags (
GATEWAY_PRESENCE_LIMITED, GATEWAY_GUILD_MEMBERS_LIMITED, and GATEWAY_MESSAGE_CONTENT_LIMITED) can be updated via the API.Icon for the app
Default rich presence invite cover image for the app
Interactions endpoint URL for the app. Must be valid according to the Receiving an Interaction documentation.
List of tags describing the content and functionality of the app (max of 20 characters per tag). Max of 5 tags.
Event webhooks URL for the app to receive webhook events
If webhook events are enabled for the app.
1 to disable, and 2 to enableList of webhook event types to subscribe to
Get application activity instance
GET
/applications/{application.id}/activity-instances/{instance_id}Activity instance object
Application ID
Activity instance ID
Unique identifier for the launch
Location the instance is running in
IDs of the users currently connected to the instance
Activity location object
Unique identifier for the location
Enum describing kind of location
ID of the channel
ID of the guild
Activity location kind enum
| Enum | Description |
|---|---|
gc | Location is a Guild Channel |
pc | Location is a Private Channel, such as a DM or GDM |