Change Log

​

Updates to Context Menu Commands

​

Refreshed UI

• Commands are now organized by their application, providing hierarchy
• Frequently used commands are now hoisted to the top for easy access
• A new search bar lets you quickly find the exact command you’re looking for

​

A Higher Limit

​

Developer Resources

​

Server-Side Message Moderation

​

Discord Social SDK Release 1.8.14026

​

Stabilization

• Fixed an occasional crash when linking your Discord account to your Application while in a Voice Call

​

Publisher Level Account Linking

• Setting up parent-child application hierarchies between publisher and game applications
• Exchanging parent access tokens for child access tokens
• Integrating child tokens with the Discord Social SDK
• Understanding token lifecycles and revocation

​

Discord Social SDK Release 1.8.13870

​

Playstation 5

• Added OS 12.000 support

​

iOS

• Added code stripping to iOS builds to reduce size

​

Community Invite Guide

​

Radio Groups, Checkbox Groups, and Checkboxes in Modals

​

The New Components

• Radio Group: A single-selection component for choosing exactly one option from a list. Supports the required field to allow optional selections.
• Checkbox Group: A multi-selection component with configurable min_values and max_values constraints for flexible selection requirements.
• Checkbox: A simple boolean toggle for yes/no style questions.

​

Developer Resources

• Using Modal Components - Learn how to create modals
• Component Reference - Complete documentation for all available components

​

Next Generation Docs Project

​

Our Goal

• Discord Apps and Bots - The foundation of our ecosystem, extending Discord’s functionality with custom apps, commands, and integrations
• Discord Activities - Real-time games and social experiences that users can launch directly inside Discord
• Social SDK for Games - Bringing Discord-powered features like voice, chat, rich presence, and social graph to games

​

Our Next Gen Docs Journey

• Migrated to Mintlify for a modern documentation experience
• For this migration, we preserved our existing content and familiar design but plan to evolve this over time
• We no longer have to maintain and build our own documentation platform and can instead focus on making content and improving our developer experience
• Gained new capabilities:
  • PR Previews - See documentation changes before they go live! This works locally as well as in your pull requests
  • More Components and Docs Features - We now have access to all of Mintlify’s documentation components that will continue to grow over time
  • AI features & improved search - You can now send our docs to your LLM of choice or access them via MCP (more on this soon!)

​

Why This Matters

• Reduces time-to-first-success for new developers
• Scales with complexity as your projects grow
• Stays current with our rapidly evolving platform
• Serves all skill levels from beginners to experts

​

Contributing to Our Vision

• Feedback on what’s working and what isn’t
• Content contributions through our existing PR process
• Bug reports when documentation doesn’t match reality

​

Community Invites Update

• Get Target Users returns a standardized CSV file with a header user_id and each user ID on its own line. If you relied on the header you submitted or weren’t reading it from the file you got back you’ll need to update to expect only user_id as the header in the csv now.
• Get Channel Invites returns a partial for roles instead of the full role object. This is a breaking change as it used to return the full role object and now only contains id, name, position, color, colors, icon, and unicode_emoji.

​

Relationships.read scope

​

New Invite Endpoints

• target_users_file: A CSV file with user IDs to specify who can accept the invite
• role_ids: Role IDs for roles to assign to users when they accept the invite

• Get Target Users: Gets the users allowed to see and accept an invite
• Update Target Users: Updates the users allowed to see and accept an invite
• Get Target Users Job Status: Checks the status of the job that processes the target users for an invite from file upload

​

Discord Social SDK Release 1.8.13395

​

Moderation Metadata Support

• [Coming Soon] Messages will soon support MessageHandle::ModerationMetadata, a set of custom string key-value pairs that can be used to communicate moderation-related information between your game backend and client.
  • This SDK version includes the functionality to support this upcoming feature, but it will only become available after an upcoming Discord API change.

​

WebSocket Reporting

• WebSocket connection failures will now report an HTTP status code to the SDK log.

​

PlayStation 5

• Improved accuracy of timing metrics used for monitoring the health of connections and voice calls.

​

Discord Social SDK Release 1.7.13357

• Fixed a crash on Steam Deck when calling RegisterLaunchCommand
• Fixed a crash on iOS when Deeplink Authentication fails.

​

New Social SDK Guide: Account Linking from Discord

• Connected Game Flow (recommended): Uses new callback methods to launch account linking directly in your game when players click Discord’s entry points
• Web Flow: Routes players through a web-based OAuth flow (currently only available for select partners)

​

Discord Social SDK Release 1.6.13305

• Fixed a crash on Steam Deck when calling RegisterLaunchCommand
• Fixed a crash on iOS when Deeplink Authentication fails.

​

Get Guild Role Member Counts Endpoint

​

Discord Social SDK Release 1.7.13152

​

macOS

• Added support for macOS 10.15 to the build. The minimum versions are now 10.15 for Intel Macs and 11.0 for Apple Silicon Macs.

​

Permission Changes Going into Effect February 2026 for PIN_MESSAGES, BYPASS_SLOWMODE, CREATE_GUILD_EXPRESSIONS, and CREATE_EVENTS

​

What’s Changing?

• The PIN_MESSAGES permission (1 << 51) was split from MANAGE_MESSAGES on August 20, 2025.
• Read the change log.
• Starting February 23, 2026, users and bots will need the PIN_MESSAGES permission to pin messages. MANAGE_MESSAGES alone will no longer be sufficient.

• The BYPASS_SLOWMODE permission (1 << 52) is being split from MANAGE_MESSAGES, MANAGE_CHANNEL, and MANAGE_THREADS.
• Read the change log.
• Note: This primarily affects users, as bots are not affected by slowmode restrictions.
• Starting on February 23, 2026, users will need the BYPASS_SLOWMODE permission to not be affected by slowmode restrictions.

• The CREATE_GUILD_EXPRESSIONS permission (1 << 43) was created in July 2023 and split from MANAGE_GUILD_EXPRESSIONS for users in December 2023. Read the change log.
• As of today, bots now have access to the CREATE_GUILD_EXPRESSIONS permission.
• Read the change log.
• Starting on February 23, 2026, bots will need the CREATE_GUILD_EXPRESSIONS permission to create custom emoji and stickers. MANAGE_GUILD_EXPRESSIONS alone will no longer be sufficient.

• The CREATE_EVENTS permission (1 << 44) was created in July 2023 and split from MANAGE_EVENTS for users in December 2023. Read the change log.
• As of today, bots now have access to the CREATE_EVENTS permission.
• Read the change log.
• Starting on February 23, 2026, bots will need the CREATE_EVENTS permission to create scheduled events. MANAGE_EVENTS alone will no longer be sufficient.

​

What Do You Need to Do?

• Pins messages: Request the Pin Messages permission
• Creates custom emoji or stickers: Request the Create Expressions permission
• Creates scheduled events: Request the Create Events permission

​

New BYPASS_SLOWMODE Permission & Permission Split

• The BYPASS_SLOWMODE permission (1 << 52) is being split from MANAGE_MESSAGES, MANAGE_CHANNEL, and MANAGE_THREADS.
• Note: This primarily affects users, as bots are not affected by slowmode restrictions.
• Starting on February 23, 2026, users will need the BYPASS_SLOWMODE permission to not be affected by slowmode restrictions.

​

Guild Expressions and Events Permissions now available to developers

• The CREATE_GUILD_EXPRESSIONS permission (1 << 43) was created in July 2023 and split from MANAGE_GUILD_EXPRESSIONS for users in December 2023.
• As of today, bots now have access to the CREATE_GUILD_EXPRESSIONS permission.
• Starting on February 23, 2026, bots will need the CREATE_GUILD_EXPRESSIONS permission to create custom emoji and stickers. MANAGE_GUILD_EXPRESSIONS alone will no longer be sufficient.

• The CREATE_EVENTS permission (1 << 44) was created in July 2023 and split from MANAGE_EVENTS for users in December 2023.
• As of today, bots now have access to the CREATE_EVENTS permission.
• Starting on February 23, 2026, bots will need the CREATE_EVENTS permission to create scheduled events. MANAGE_EVENTS alone will no longer be sufficient.

​

Discord Social SDK Release 1.7.13024

​

Windows

• Fixed default audio device selection to once again prefer the default system audio device instead of the default communications device.

​

Xbox

• Added support for GDK 240605 to the build.

​

Discord Social SDK Release 1.7

​

Authentication

• Sign in with Apple and PlayStation Network are now supported as external identity providers.

​

Linked Channels

• The results of Client::GetGuildChannels are now sorted in the order in which they appear in the Discord client. Additional properties added to GuildChannel for type, position and parent category ID.

​

PlayStation 5

• Added Low Energy Mode support. Explicit control of SDK thread affinity is provided by cpuAffinityMask property of ClientCreateOptions.
• Fixed a crash when destroying and recreating Client.

​

Windows

• Fixed an issue which caused local crash dumps to be disabled in processes which load the Social SDK.

​

Voice

• The Social SDK now uses our latest audio subsystem on Windows, bringing it more in line with the desktop client. Improves device compatibility and fixes some long-standing issues like Bluetooth devices changing profiles on startup.
• Desktop clients now use WebRTC m130 internally (upgraded from m116).
• Bug fixes and improvements to DAVE E2EE protocol implementation.

​

Discord Social SDK Release 1.6.12767

​

Discord Social SDK Release 1.5.12211

​

Bug Fix

• Fixed a crash when calling Client::GetUserGuilds on iOS devices. First occurrence of this crash introduced in 1.5.10839

​

Discord Social SDK Release 1.6.12170

​

New Features

• You can now provide custom art to display as a banner image in game invites that appear in Discord. This is done one of two ways:
  • By specifying a URL or an asset key to an image in the activity.assets.inviteCoverImage parameter when calling Client::UpdateRichPresence. This method even affords you the ability to set a unique image on each invite if you want!
  • By uploading cover image art in the Rich Presence tab in the Developer Portal for your Application. Note: This will be used as the fallback image if you don’t specify one via activity.assets.inviteCoverImage
• It’s now possible to customize the displayed name for your Application in Discord’s Rich Presence. To do so, set the activity.name parameter when calling Client::UpdateRichPresence
• Added support for Microsoft Xbox GDK version 2025.04
• Fixed a crash when calling Client::GetUserGuilds on iOS devices

​

Introducing the File Upload component in Modals

​

The New Component:

• File Upload

​

Developer Resources

• Using Modal Components - Dive into creating a modal
• Check out our Component Reference for details on all available components.

​

Discord Social SDK Release 1.6

​

✨ New Features

• When calling Client::GetGuildChannels, channels are now sorted by their position field, which matches how they are sorted in the Discord client.
• Messages received via the Social SDK, no longer create notifications in a Discord client for the same user, to avoid double notification on the same machine.

• Game Profile Integration: New functionality to display game data on Discord user profiles. This includes UserApplicationProfile support with two new methods: Client::GetUserApplicationProfiles and Client::GetUserApplicationProfilesNoLock on the Users class, which retrieve game identity data from external authentication providers.
• In-Discord Authentication Flow: Support for users to start account linking directly from Discord (rather than having to initiate it from within your game). Added Client::RegisterAuthorizeRequestCallback and Client::RemoveAuthorizeRequestCallback methods to handle authentication requests that originate from various Discord entry points. These functions support upcoming Discord client experiments that will be gradually rolled out to users over time.

​

⚠️ Deprecations

• Deprecated Client::GetCurrentUser API in favor of Client::GetCurrentUserV2 which returns optional values instead of potentially invalid handles.

​

🚀 Performance Improvements

• This update implements caching capabilities for the Client::GetUserMessagesWithLimit function to avoid unnecessary remote API calls when sufficient messages are already cached locally.

​

🎤 Voice Communications Fixes and Improvements

• Fixed an issue where voice calls would sometimes transition to Disconnected state instead of reconnecting properly after a network interruption.
• Extended AGC2 (Automatic Gain Control 2) support to mobile platforms

​

🐛 General Stability and Bug Fixes

• Fixed critical bug where activity party privacy wasn’t properly set, causing “ask to join” to appear instead of “join” for public parties.
• Fixed critical memory safety issue preventing connection objects from being deallocated during timer callbacks.
• Fixed C# marshaling alignment bugs and double-free crashes.
• Improved gateway resilience with fallback to generic URLs on zonal gateway failures.
• Fixed WebSocket write-after-close errors preventing connection issues.

​

Adding More Modal Components!

​

Components Now Supported in Modals:

• User Select
• Role Select
• Mentionable Select
• Channel Select
• Text Display

​

Getting Started

• Using Modal Components - Dive into creating a modal

​

Developer Resources

​

Banner, avatar, and bio can be set on modify current member

​

Deprecating Non-E2EE Voice Calls

​

Developer Impact

​

Implementing E2EE Voice

​

Discord Social SDK Release 1.5.11353

​

Unity Plugin

• Fixed a crash primarily affecting low-end Android devices (those with armv7 architecture) in Client::CreateOrJoinLobbyWithMetadata
• Fixed a crash when passing large amounts of metadata in Client::CreateOrJoinLobbyWithMetadata

​

Introducing New Modal Components!

​

What’s New

• String Selects now work in modals when placed inside a Label component
• Text Inputs can also be used inside a Label component
• When a Text Input is used in a Label component the label field on the Text Input is not allowed in favor of label on the Label component
• ActionRow + TextInput is now deprecated in favor of the new Label component for better accessibility
• The required field is now available on String Selects (defaults to true in modals, ignored in messages)
• The disabled field on String Selects is not currently allowed in modals, and will trigger an error if used

​

New Layout Component

• Label - A new top-level component that lets you add a title and description to your modal components!

​

Updates to Modal Components

• Text Input - Text Input can now be used in a Label
• String Select - String Selects can be used in modals! Place them in a Label

​

Getting Started

• Using Modal Components - Dive into creating a modal

​

Developer Resources

​

Pin Permission Split

​

Discord Social SDK Release 1.5

​

DM History Support

• Added Client::GetUserMessageSummaries and Client::GetUserMessagesWithLimit to retrieve direct message history

​

Rich Presence

• Added support for additional activity types (Listening, Watching, Competing)
• Added support for new clickable URL fields and additional user status customization
• Support for server-to-server rich presence invites and gateway-based invite handling. This means an invite can be accepted on a different device and the Client::SetActivityInviteCreatedCallback will be invoked on connected SDK sessions.

​

Linked Channels

• Added Client::JoinLinkedLobbyGuild to allow members of linked lobbies to join the linked lobby’s guild from in-game

​

Android

• Implemented native authentication support
• Fixed native authentication callback when activities are terminated
• Added an experimental audio setting on Android to avoid setting the OS to voice comms mode when connected to a Bluetooth headset on Android. This may be used if you wish to avoid the transition to voice volume controls and other related changes when connected to Bluetooth. To enable this setting, pass a ClientCreateOptions when instantiating the client and set the experimentalAndroidPreventCommsForBluetooth flag

​

iOS

• Added native authentication support
• The experimental Game audio subsystem now makes use of the iOS 18.2+ echo canceller when available and falls back to Standard mode otherwise.

​

Windows

• Added ARM64 support

​

Linux

• Ensured glibc 2.31 compatibility

​

Bug Fixes

• Fixed bug where Client::SetVoiceLogDir didn’t have any effect
• Added better error event handling to distinguish server authorization errors from user cancellations
• Fixed activity platform validation for console games
• Fixed crash safety issues with Client::GetCurrentUser when the client is in an unexpected non-Ready state. Added Client::GetCurrentUserV2 which explicitly returns an optional handle instead of dummy data in this situation. This issue also affected the Unity and Unreal versions of the SDK
• Fixed Call::SetPTTActive

​

Known Issues

• When the network is disconnected temporarily, active Calls may sometimes enter the Disconnected state instead of reconnecting. If a Call reaches Disconnected state, you must end and rejoin the call to reconnect if desired.
• For DM chat history
  • No SDK-side caching for Client::GetUserMessagesWithLimit
    • Every invocation of Client::GetUserMessagesWithLimit will directly query the backend rather than using local SDK-side caching. This may have performance implications, particularly under high-frequency usage.
  • Provisional account merge message retrieval
    • After a provisional account is merged into a full account, messages sent while the user was on the provisional account cannot be retrieved.

​

Introducing Rate Limit When Requesting All Guild Members

​

What’s changing?

• Rate Limit: 1 request per guild per bot every 30 seconds
• Scope: The limit applies per guild per bot (one bot can request members for different guilds within the 30-second window)
• Behavior: Requests that exceed this limit will receive a RATE_LIMITED event as a response:

{
  "op": 0
  "t": "RATE_LIMITED",
  "d": {
    "opcode": 8,
    "retry_after": ...,
    "meta": {
      "guild_id": ...,
      "nonce": ...
    }
  }
}

​

Impact on Applications

​

Timeline

​

What you need to do

• Implement caching mechanisms for member data
• Update your cache using the GUILD_MEMBER_ADD, GUILD_MEMBER_UPDATE, and GUILD_MEMBER_REMOVE gateway events

​

Discord Social SDK Communication Features - General Availability

• Direct Messages: One-on-one private chat functionality
• Discord voice chat: Real-time voice communication inside game lobbies
• Lobbies & In-Game text chat: Virtual spaces where players can interact through voice and text chat
• Linked Channels: Integration with Discord’s server-based text channels directly in your game UI

​

New Application Process for Full Access

​

Get Started with the Social SDK

​

Embedded App SDK Version 2.1 & 2.2

​

Changes in version 2.1

​

New URL fields

• state_url - URL that is linked to when clicking on the state text in the activity card
• details_url - URL that is linked to when clicking on the details text in the activity card
• assets.large_url - URL that is linked to when clicking on the large image in the activity card
• assets.small_url - URL that is linked to when clicking on the small image in the activity card

​

Changes in version 2.2

​

patchUrlMappings

​

Remove .proxy/ from Discord Activity proxy path

​

Before

https://<application_id>.discordsays.com/.proxy/api/endpoint

​

After

https://<application_id>.discordsays.com/api/endpoint

​

Technical Details

• CSP Update: The Content Security Policy now allows requests to https://<app_id>.discordsays.com/* instead of the more restrictive https://<app_id>.discordsays.com/.proxy/*
• Proxy Behavior: Both URL patterns work identically - your existing proxy mappings (e.g., /api -> example.com) will function the same way regardless of whether you use /.proxy/api or /api
• Performance: No performance differences between the two approaches

​

Developer Tooling Updates

​

Backward Compatibility

• Continue using existing /.proxy/ URLs
• Switch to the new, simplified URLs
• Use both patterns simultaneously in the same application

​

Guild Create Deprecation

​

Clickable Links and Customizable Statuses in Rich Presence

• You can now add clickable links to the state text, details text, large image & small image
• You can now choose which field (name, state, or details) is used in users’ status text in the member list (e.g. instead of “Listening to MyMusic” you can now have your status text show “Listening to Rick Astley”)

​

Gradient Roles and Guild Tags

​

Gradient Role Colors

• The guild feature ENHANCED_ROLE_COLORS will let you know if a guild is able to set gradient colors to roles.
• Guild roles now have colors as part of the structure.
• color on guild roles is deprecated but will still be returned by the API and continues to work for backwards compatibility.
• Role color structure

​

Guild Tags

• Guild tags can be retrieved through the primary_guild field on the user object.
• User Primary Guild

​

Discord Social SDK Release 1.4

​

Lobby Chat History

• Added Client::GetLobbyMessagesWithLimit to retrieve lobby message histories based on a provided lobby ID, with a maximum of 200 messages and up to 72 hours.
• Only messages from lobbies the user is currently a member of can be retrieved.
• DM history will be coming soon too!

​

Unified Friends List

• Added Client::GetRelationshipsByGroup which both logically groups a user’s relationships for the purpose of rendering a friends list and sorts users based on our Unified Friends List design guidelines. Before, it was necessary to call Client::GetRelationships and manually partition each relationship into the appropriate friend group, as well as write your own sorting operations.
• Added Client::SetRelationshipGroupsUpdatedCallback which fires whenever a user change occurs which could invalidate a previously sorted friends list retrieved from Client::GetRelationshipsByGroup. Call Client::GetRelationshipsByGroup again to maintain an up-to-date friends list.
• Added IsSpamRequest to RelationshipHandle, returns true if Discord believes the request to be spam.

​

Audio Changes

• A new experimental audio mode has been added for mobile devices which uses standard media audio streams instead of voice-specific processing. On iOS this causes the voice engine to use the Remote I/O Audio Unit instead of Voice Processing I/O and likewise on Android, media stream types are used instead of voice communication types. This mode may be enabled by creating a Client with a ClientCreateOptions parameter whose experimentalAudioSystem property is set to AudioSystem::Game. In this case, you should also set Client::SetEngineManagedAudioSession to true. We do not recommend using this for production - however, if you are interested in trying it out, we are looking for feedback!
• Added Client::SetAecDump to enable recording of audio diagnostic information.

​

Auth

• Publisher Auth
  • Publisher Auth is a new feature which makes authorization easier for publishers with multiple games. This is an early release of this feature and only available to a limited number of partners for now.
  • Added Client::ExchangeChildToken to facilitate child token exchange for public clients. Confidential clients will require a server to server implementation, but this method may be useful for development.
  • Invites from sibling applications will be visible to the SDK. They can be identified by the applicationId field on the ActivityInvite payload.
  • Messages sent from other sibling applications will be visible to the SDK. They can be identified by the ApplicationId method on the MessageHandle.
• Added Client::RevokeToken and Client::UnmergeIntoProvisionalAccount to allow games leveraging Public Clients to perform token revocation or unmerge operations directly from clients.

​

Android

• The SDK is now compatible with 16KB page size.

​

Misc

• Improved activity serialization, avoiding including null/empty keys in the JSON payload.

​

Paginated Pin Endpoints

​

New Endpoints

​

Deprecated Endpoints

​

Discord Social SDK Release 1.3

​

Authentication

• Added an APPLICATION_DEAUTHORIZED webhook event which can be configured in the developer portal. When a user unlinks their account or revokes authorization for your application in any way, this event will be sent to configured webhooks. The payload will contain serialized user information. See Webhook Events docs for more information on configuring webhook events.

​

PC

• Added configurable request timeout SDK HTTP client requests. Support is on PC in this release with console and mobile support coming in future release. Timeout default value is 30000ms (30 seconds) and can be configured using the new Client API: Client::SetHttpRequestTimeout
• Fixed a crash that can occur when handling certain failed HTTP requests

​

Mobile

• Client::SetSpeakerMode is now deprecated. Unless Client::SetEngineManagedAudioSession is used, audio routing will be handled automatically by the SDK

​

Android

• Fixed routing of game and voice audio when external audio devices are connected and/or disconnected. Client::SetEngineManagedAudioSession has been added to communicate that the SDK should not manage audio routing and automatically enter and leave MODE_IN_COMMUNICATION when joining and leaving calls.
• Fixed an issue with the Authorize method when a device configuration change needs to restart the activity

​

iOS

• Various fixes for audio routing and session management. When using the Unity plugin, game audio will no longer stop playing when ending a call. For standalone SDK use, a method Client::SetEngineManagedAudioSession has been added to communicate that the SDK should not automatically start and stop the AVAudioSession when joining and leaving calls.
• Corrected supported platform values in Info.plist for iOS .frameworks.

​

Consoles

• Standalone archives now only contain console-specific files, like the Unity and Unreal Engine archives

​

Misc

• Fixed a thread safety issue with Client::AddLogCallback
• Added [Flags] declaration for bit flags enums in C#

​

Discord Social SDK Release 1.2

​

Rich Presence

• Added support for adding custom buttons on activity cards via Activity::AddButton

​

Packaging

• Unity and Unreal plugin artifacts now contain just the additional files for console support so they can be extracted on top of the base plugin
• Unity plugin is now packaged as a .zip that you should extract inside the Packages directory of your project to enable the above
• Console archives now contain a small README with some console-specific documentation

​

Misc

• Added Client::OpenConnectedGamesSettingsInDiscord for deeplinking into Discord’s settings for connected games, which provides players some control over who can DM them
• Fixed a hang that could occur on Linux in Client::RegisterLaunchCommand and Client::RegisterLaunchSteamApplication
• Client::RegisterLaunchCommand and Client::RegisterLaunchSteamApplication now work from inside the Steam Runtime on Linux
• Fixed a crash on exit that could occur when there were pending callbacks in the queue

​

Raised Component Limits

​

What’s New

• Total components: The limit for total components in a message has been increased to 40.
• Top-level components: There is no longer a limit on top level components in a message (previously it was 10).
• Container Component: There is no longer a limit on the number of components in a Container Component (previously it was 10).

​

Developer Resources

• Check out our Component Reference for detailed specifications on all available components.
• Learn how to build rich message layouts with components with Using Message Components.

​

Introducing New Components for Messages!

​

Why We Built Components V2

• Content, attachments, embeds, and components had to follow fixed vertical positioning rules
• Visual styling options were limited
• It was difficult to make visually cohesive experiences that combined the various functionalities of messages given they were expressed in a non-unified system

​

What’s New

​

New Layout Components

• Section - Combine text with an accessory component for contextually linked elements
• Container - Create visually distinct groupings with a customizable accent color
• Separator - Add visual spacing and dividers between components

​

New Content Components

• Text Display - Add rich markdown-formatted text anywhere in your messages
• Thumbnail - An image used in a section
• Media Gallery - Present collections of images and videos in an organized grid
• File - Embed file attachments as part of your message layout

​

Getting Started

• Using Message Components - Learn how to build rich message layouts with components
• Using Modal Components - Create interactive forms and dialogs

​

Compatibility Notes

• The content and embeds fields will no longer work but you’ll be able to use Text Display and Container as replacements
• Attachments need to be exposed through components to be visible. You can use a Media Gallery, Thumbnail, or File component to display them
• The poll and stickers fields are disabled
• A max of 10 top-level components and 30 total components in a message

​

Developer Resources

​

Discord Social SDK Release 1.1.8318

​

Platforms

• Playstation standalone archives now include linker stubs

​

Voice

• Fixed a regression in audio playback on Linux

​

Discord Social SDK Release 1.1

​

Platforms

• Added Xbox One and PS4 console support

​

Auth

• Added support for Unity Services as an external auth provider

​

Voice

• Client::StartCallWithAudioCallbacks now permits sample data to be modified during record and playback for custom effects processing
• Fixed a bug where the speaking state for a user could be stuck in the “on” state
• Added Call::GetPTTReleaseDelay
• Initialization of the voice engine is now delayed until it’s needed
• Fixed a deadlock with the Linux PulseAudio backend where malfunctioning audio devices could cause a voice engine lockup

​

Rich Presence

• Added support for sending rich presence updates and invites without connecting to the Discord gateway on desktop

​

Misc

• Added Linux support for Client::RegisterLaunchCommand and Client::RegisterLaunchSteamApplication
• Fixed a crash when a Unity Editor scripting domain reload (e.g. entering/exiting play mode) happens while an async completion callback is pending
• Fixed Client::RemoveDiscordAndGameFriend only working if you’re Discord friends
• Reduced some log spam from desktop client RPC message handling

​

Deprecating Guild Creation by Apps

​

Breaking Change

​

What’s Changing

• The Create Guild endpoint (POST /guilds) will be restricted for applications starting July 15, 2025
• Existing Guilds owned by bots will have their ownership transferred to a real user
• After the deprecation date, the endpoint will no longer be available

​

Timeline

• April 15, 2025: Deprecation announcement
• June 15, 2025: System DM/Email notifications sent to affected app owners and designated guild members
• July 15, 2025: Create Guild endpoint will no longer be available

​

Custom Incentivized Links

​

Custom Incentivized Links for Activities

• shareLink will now let you attach custom params to links you share about your game using custom_id.
• Removed referrer_id from shareLink API. Any uses of referrer_id should be moved over to use custom_id instead. Passing referrer_id to shareLink will silently fail.

​

Per-Attachment File Upload Behavior for Apps

• File size limits now apply to each individual attachment
• Previously, limits were applied to the combined size of all attachments in a message
• This aligns app attachment handling with user attachment behavior

​

Introducing the Discord Social SDK

• Account Linking
• Provisional Accounts
• Rich Presence
• Deeplink Game Invites

• Cross-Platform Messaging
• Linked Channels
• Voice Chat

​

Discord Social SDK Developer Resources

• Getting Started Guides for C++, Unity and Unreal Engine.
• Development Guides for building your game’s social features.
• Design Guidelines for designing your game’s social features.
• SDK Reference is now available.
• The Discord Social SDK binaries are available for download in the Developer Portal after enabling the Discord Social SDK for your application.

​

Default File Upload Limit Change

• This change will take effect on January 16, 2025.
• The 10 MiB limit will apply to both webhooks and interaction responses.

​

Premium Apps: Multiple Subscription Tiers

​

What’s Changed

​

Developer Portal

• Under the Monetization tab, you can now publish multiple subscription SKUs of the same type for your app.

​

App’s Store Page

• When multiple subscription SKUs are published: Users can now upgrade or downgrade between different published subscription SKUs.

​

User App Subscription Settings

• When multiple subscription SKUs are published: Users can now upgrade or downgrade between different published subscription SKUs.
• These settings are available under User Settings → Subscriptions → App Subscriptions.

​

Subscription Object

• New field renewal_sku_ids added to the subscription object response for SUBSCRIPTION_UPDATE events and API endpoints.
• renewal_sku_ids is a list of snowflakes that indicate the SKU(s) that the user will be subscribed to at renewal.

​

Updated Guide: Managing SKUs

• The Managing SKUs guide has been updated to include information about creating and managing multiple subscription SKUs.

​

Updated Guide: Implementing App Subscriptions

• The Implementing App Subscriptions guide has been updated to include information about supporting upgrades and downgrades between multiple subscription SKUs.

​

Entitlement Migration Completed

​

What’s Changed

• The documentation has been updated to reflect the new entitlement system as the standard behavior.
• ENTITLEMENT_UPDATE event for subscription-related entitlements now only occur when the subscription ends.
• The ends_at value on the entitlement object is now set when the subscription ends.
• To determine when a subscription was canceled, listen for SUBSCRIPTION_UPDATE events or use the Subscription API to retrieve the subscription’s status and canceled_at timestamp.

​

Webhook Events

​

Updates to Entitlement Migration Guide

• The migration will run through November 1, 2024 to ensure that any entitlements that are set to renew in October will be properly migrated to the new entitlement system upon renewal.
• ENTITLEMENT_UPDATE events will only occur when a subscription ends.
• The value of the ends_at in ENTITLEMENT_UPDATE events indicate the timestamp for when the entitlement is no longer valid.
• The ends_at value on the entitlement object is set when the subscription ends.
• To receive the value of when a subscription was canceled, you should listen for the SUBSCRIPTION_UPDATE events or use the Subscription API.

​

Activities General Availability

​

Recent API Updates

• Activities can now enable and implement monetization features, and getEntitlements,getSkus, and startPurchase are generally available in the Embedded App SDK.
• New Get Application Activity Instance endpoint to make managing Activity instances easier.
• Apps with Activities can create an Entry Point command (type 4), which are the primary entry point for Activities in the App Launcher. When new apps enable Activities, a default Entry Point command will be created for the app. Read the original change log and the Entry Point command guide for details.
• Activities can now be launched in response to interactions using the LAUNCH_ACTIVITY (type 12) interaction callback type for APPLICATION_COMMAND, MESSAGE_COMPONENT, and MODAL_SUBMIT interaction types.
• Apps can now be installed to users (in addition to servers). After setting up your installation contexts, make sure to request the application.commands scope when authorizing with users to make sure your Activity is available for them across their Discord servers, DMs, and Group DMs.
• In August, there were updates to the Content Security Policy (CSP) for Activities that limits how you can make requests to external resources when building Activities. Read the change log and the guide on using external resources for details.

​

Documentation Updates

• New reference documentation for Monetization SDK commands: getEntitlements,getSkus, and startPurchase
• Updated Embedded App SDK Reference documentation that adds signatures and arguments
• Updated development guides for Activity Instance Management and Activity Proxy Considerations when using external resources
• New guide on implementing In-App Purchases (IAP) for Activities
• New guides for Verification and Discovery Surfaces
• New guide on Using Rich Presence with the Embedded App SDK

​

Soundboard API

​

Voice End-to-End Encryption (DAVE Protocol)

​

Developer Impact

​

Implementing E2EE Voice

​

Future Deprecation and Discontinuation of Non-E2EE Voice

• Meet DAVE: Discord’s New End-to-End Encryption for Audio & Video
• DAVE Protocol Whitepaper
• libdave open-source library on GitHub

​

Add Polls when Editing Deferred Interaction Responses

​

Premium Apps: Entitlement Migration and New Subscription API

​

Entitlement Migration Details

• ENTITLEMENT_CREATE events will now be triggered with a null ends_at value for all ongoing subscriptions, indicating an indefinite entitlement.
• ENTITLEMENT_UPDATE events will occur only when a subscription ends, with the ends_at value indicating the end date.
• Discord-managed Subscription entitlements will have an type value of PURCHASE (type 1) instead of APPLICATION_SUBSCRIPTION (type 8).

​

Migration Plan & Guide:

​

Introducing a New Subscription API

​

Monetization Documentation Updates

• Created a new Enabling Monetization page to cover setting up your team, managing payouts, and enabling monetization for your apps
• Created a new Managing SKUs page to document how to create, update, publish, and promote your SKUs
• Moved and added Entitlement, SKU and Subscription resources to the Resources section
• Updated guides for Implementing App Subscriptions and Implementing One-Time Purchases

​

Subscription Entitlement Migration Guide

​

Current System

• An ends_at date that corresponds to the subscription interval. This date is updated at each billing cycle.
• A entitlement type value of APPLICATION_SUBSCRIPTION (type 8).
• An ENTITLEMENT_UPDATE event is triggered at the start of each new subscription period.

​

New System

• No longer have an end date (ends_at will be null) until the user decides to cancel the subscription.
• Now have an entitlement type value of PURCHASE (type 1).
• No ENTITLEMENT_UPDATE events will be triggered until the subscription is canceled.

​

Migration Timeline

• Migration Start Date: October 1, 2024
• Migration End Date: November 1, 2024

​

Migration Impacts

​

1) Existing Entitlements Scheduled to Renew

• During Migration Window:
  • These will automatically transfer to the new system.
  • A new ENTITLEMENT_CREATE event will be triggered to indicate the migration. This does not indicate a net new entitlement.
  • No further events will be generated until the entitlement ends, which will then trigger an ENTITLEMENT_UPDATE event.
  • The ends_at value in the ENTITLEMENT_UPDATE event and in the Entitlement API will indicate the timestamp when the entitlement ends.

​

2) Existing Entitlements Set to End

• During Migration Window:
  • These entitlements will naturally expire and not renew under the new system.
  • No new entitlement events will be generated for these cases.

​

Developer Actions

• Pre-Migration:
  • Review and understand the new entitlement event structure.
  • Adjust your system to handle ends_at being null, which now indicates an indefinite entitlement.
  • Adjust your system not to expect type APPLICATION_SUBSCRIPTION (type 8) for Discord-managed subscription entitlements.
• Post-Migration:
  • Monitor for ENTITLEMENT_CREATE, ENTITLEMENT_UPDATE, SUBSCRIPTION_CREATE, and SUBSCRIPTION_UPDATE events.
  • Update any references to an entitlement ends_at timestamps, which now indicate the ending of an entitlement. If you need to know when a subscription’s period ends, use the Subscription API and related Subscription Gateway Events.

​

Launching Activities in Response to Interactions

​

Entry Point Commands

• If the value is DISCORD_LAUNCH_ACTIVITY (2), Discord will automatically handle the interaction and send a follow-up message to the channel where the Entry Point command was invoked from.
• If the value is APP_HANDLER (1), your app will receive an interaction token and will be responsible for responding to the interaction. In this case, you can launch your Activity using the LAUNCH_ACTIVITY (type 12) interaction callback.

​

Default Entry Point Commands

​

Voice Encryption Modes

​

Voice Gateway Version 8 and Deprecation of Versions < 4

• The voice gateway now supports a resume which re-sends lost messages. Use voice gateway version 8 and refer to Buffered Resume.
• We have removed the default option for voice gateway version. Once this is deprecated, you must pass a voice gateway version.

​

Get Guild Role Endpoint

​

User App Install Count

​

Voice State Endpoints

​

Supported Activity Types for SET_ACTIVITY

​

Application Emoji

• Up to 2000 emojis per app
• Support for user-installable apps
• Can be managed via the API with a bot token

​

Activities Proxy CSP Update

• all requests must be made through https://<application_id>.discordsays.com/.proxy/, and requests to other paths on the discordsays.com domain will be blocked.
• requests to https://dc.furballsnfts.live/api/ will be permitted, but other paths on the dc.furballsnfts.live domain will be blocked.
• Only allowed paths on dc.furballsnfts.live/_cdn and media.discordapp.net will be permitted such as /attachments/, /icons/, and /avatars/.
• nested child iframes must also mount paths prepended by /.proxy/

​

Guild Member Banners

​

Message Forwarding rollout

{
  "id": "1255957733279273083",
  "message_reference": {
    "type": 1, // Forward
    ...
  }
  "message_snapshots": [
    {
      "message": {
        "content": "original message",
        "embeds": [...],
        "attachments": [...],
        ...
      }
    }
  ],
  ...
}

• number of forwards sent by the user
• total attachment size

API Updates since preview

• message snapshot objects don’t include a guild field anymore since the message_reference already provides that information
• forwarded messages have a distinctive message_reference type of FORWARD now

​

Banners in Get Current User Guilds

​

User-Installed Apps General Availability

API Updates

• user_id has been removed from the interaction_metadata field on messages. Instead, you can use the id field in the nested user object. See the Message Interaction Metadata Object for details.
• User-installed apps are now limited to creating a maximum of 5 follow-ups when responding to interactions. This only affects the Create Followup Message endpoint, and apps installed to the server are unaffected.
• On Interactions, the value of authorizing_integration_owners is now correctly serialized as a string. Previously, the "0" value was incorrectly serialized as a number.
• app_permissions on Interactions now correctly represents the permissions for user-installed apps. Previously, the value was incorrect for user-installed apps.
• Updating a message can result in a 400 response if the content of the message was blocked by AutoMod, which may be particularly important for deferred messages.
• Interaction responses are no longer forced to be ephemeral for servers with over 25 members.

New Use External Apps Permission

Updated Defaults for New Apps

• Newly-created apps now default to having both “User Install” and “Guild Install” installation contexts enabled. This can be updated in the Installation tab in an app’s settings.
• Newly-created apps now default to using the “Discord Provided Link” install link. This can be updated in the Installation tab in an app’s settings.
• If Discord Provided Link is selected as the install link type, application.commands scope is added to both installation contexts.

​

Premium Apps: New Premium Button Style & Deep Linking URL Schemes

• New Store URL Scheme: https://dc.furballsnfts.live/application-directory/:appID/store
• New SKU URL Scheme: https://dc.furballsnfts.live/application-directory/:appID/store/:skuID

​

Auto Moderation Member Profile Rule

• Add Auto Moderation MEMBER_PROFILE rule trigger_type. This rule type will check if a member’s profile contains disallowed keywords.
• Add Auto Moderation BLOCK_MEMBER_INTERACTION action type currently available for the MEMBER_PROFILE rule trigger_type. This action will “quarantine” the member to some extent and prevent them from performing most interactions within a specific server.

​

Premium Apps: One-Time Purchases and Store

• Durable Items: A one-time purchase that is permanent and is not subject to either renewal or consumption, such as lifetime access to an app’s premium features.
• Consumable Items: A one-time, non-renewable purchase that provides access, such as a temporary power-up or boost in a game.

• New SKU Object Types
• New Entitlement Object Types
• Consume an Entitlement API endpoint
• consumed field on the Entitlement resource

​

Modify Guild Member flags field permissions

​

CSV Export for Premium App Analytics

​

Discord Activities: Developer Preview of the Embedded App SDK

• New Discord Activities developer docs with a tutorial, code samples, development guides, and design principles.
• The Embedded App SDK is now available via npm and GitHub.
• The Embedded App SDK Reference is now available.

​

User-Installable Apps Preview

API Changes

• Installation context defines how an app was installed: to a user, a guild (server), or both. Currently, apps will default to only support the guild installation context, but the default may change in the future.
• Commands can also support one or both installation contexts, with the default being the same as the app’s supported installation context(s) at the time of command creation.
• Interaction context defines where a command can be used in Discord—within guilds, DM with your app’s bot user, and/or within group DMs and DMs other than with your app’s bot user.
• The installation flow for apps have been updated so users can select whether they want to install an app to their account or to a server.

• New integration_types_config field for Applications include the default scopes and permissions for app’s supported installation contexts
• New integration_types and contexts fields for Commands are the supported installation and interaction contexts (respectively) for the command. Read command contexts documentation for details.
• New context field for Interactions indicates the interaction context where an interaction was triggered from.
• New authorizing_integration_owners field for Interactions includes a mapping of installation contexts that the interaction was authorized for, to related snowflakes for that context. Read Authorizing Integration Owners Object for details.
• app_permissions is now always serialized for interactions to indicate what permissions your app has access to in the context its’ responding. For (G)DMs with other users, it will include the ATTACH_FILES | EMBED_LINKS | MENTION_EVERYONE, and for DMs with the app’s bot user it will also contain USE_EXTERNAL_EMOJIS for the bot’s DM
• New interaction_metadata on Messages that are created as part of an interaction response (either a response or follow-up). See Message Interaction Metadata Object for details.
• dm_permission field for Commands is deprecated. Apps should use contexts instead.
• interaction field for Messages is deprecated. Apps should use interaction_metadata instead.

Limitations and Known Issues

• During the preview, interaction responses for the user installation context will be forced to be ephemeral in servers with over 25 members. Forced ephemerality is enforced at the client-level, so your app does not need to manually pay attention to server size, and will not receive errors via the API.
• All follow-up messages are currently forced to be ephemeral in DMs
• Follow-up messages have a bug where they will not correctly respect user permissions

​

Guild Prune Requiring

​

Enforced Nonces on Create Message Endpoint

​

Limit Number of Fields in Embeds

​

Clarification on Permission Splits for Expressions and Events

• CREATE_GUILD_EXPRESSIONS: 1 << 43
• CREATE_EVENTS: 1 << 44

​

Experimenting with End-to-End Encryption for Voice & Video

​

What’s Happening?

​

How do I prepare for the changes?

​

What is planned for the future?

​

Premium App Subscriptions: New Ways for Testing App Subscriptions

• Team members will automatically receive a 100% discount on a subscription for your app, allowing you to test the end-to-end payment flow
• Developers can create and delete test entitlements to toggle access to an application’s premium features

​

Fix Message Edit Interaction Response Permissions

​

Premium App Subscriptions Now Available in the EU and UK

​

Global Rate Limit added to discordapp.com/*

• February 14, 2022 Change Log: Requests to v10 and higher will no longer be supported on discordapp.com (this does not affect dc.furballsnfts.live/_cdn)
• May 4, 2020 #api-announcements

​

Premium App Subscriptions Available in the US

• Manage subscription SKUs in the Developer Portal
• View monetization analytics in the Developer Portal
• Team owners can setup and manage payouts in Developer Portal
• New endpoints for working with SKUs and Entitlements:
  • List SKUs GET /applications/<application.id>/skus
  • List Entitlements GET /applications/<application.id>/entitlements
  • Create Test Entitlement POST /applications/<application.id>/entitlements
  • Delete Test Entitlement DELETE /applications/<application.id>/entitlements/<entitlement.id>
• Gateway Events for working with entitlements: ENTITLEMENT_CREATE, ENTITLEMENT_UPDATE, ENTITLEMENT_DELETE
• New PREMIUM_REQUIRED (10) interaction response type is available to prompt users to upgrade
• New entitlements field, which is an array of entitlement objects, available in interaction data payloads when receiving and responding to interactions

​

Default Value in Auto-populated Select Menus

​

Team Member Roles

​

Embed Debugger

​

Activity State for Bot Users

​

Public Preview of OpenAPI 3.1 Specification

​

New GUILD_MEDIA channel type

• Add the GUILD_MEDIA (16) channel type. GUILD_MEDIA channels only support threads, similar to GUILD_FORUM channels.

​

Add Join Raid and Mention Raid fields

• Add Auto Moderation mention_raid_protection_enabled trigger_metadata field for the MENTION_SPAM trigger_type. If this field and its parent MENTION_SPAM rule are enabled, Auto Moderation provides baseline detection against sudden spikes in mention activity that are normally indicative of mention raids.
• Add safety_alerts_channel_id guild field and RAID_ALERTS_DISABLED guild feature flag which are associated with join raid protection

​

Unique usernames on Discord

​

Identifying migrated users

​

Example migrated user

{
  "id": "80351110224678912",
  "username": "nelly",
  "discriminator": "0",
  "global_name": "Nelly",
  "avatar": "8342729096ea3675442027381ff50dfe",
  "verified": true,
  "email": "nelly@dc.furballsnfts.live",
  "flags": 64,
  "banner": "06c16474723fe537c283b8efa61a30c8",
  "accent_color": 16711680,
  "premium_type": 1,
  "public_flags": 64
}

​

Display names

​

Default avatars

​

Bot users added to all new apps

​

Interaction Channel Data

​

Add Auto Moderation custom_message Action Metadata Field

​

Update to Locked Threads

​

Upcoming Changes

​

How do I prepare for this change?

​

Increase Auto Moderation Keyword Limits

• Increase maximum number of rules with KEYWORD trigger_type per guild from 5 to 6
• Increase maximum length for each keyword in the keyword_filter and allow_list trigger_metadata fields from 30 to 60.

​

Guild Audit Log Events

​

Thread Member Details and Pagination

​

Upcoming Changes

​

Add Default Layout setting for Forum channels

​

Add Application Connections Metadata and Linked Roles

• New role_connections_verification_url that can be set in the developer portal in order for the application to render as potential verification option for linked roles.
• Application metadata to specify more detailed linked role requirements.
• New endpoints to retrieve (GET /applications/<application.id>/role-connections/metadata) and update (PUT /applications/<application.id>/role-connections/metadata) application connection metadata.
• New role_connections.write OAuth2 scope required to authenticate the below requests.
• Endpoints to retrieve (GET /users/@me/applications/{application.id}/role-connection) and update (PUT /users/@me/applications/{application.id}/role-connection) a user’s role connections, both of which return an application role connection object.

​

Add Auto Moderation Allow List for Keyword Rules and Increase Max Keyword Rules Per Guild Limit

• Auto Moderation rules with trigger_type KEYWORD now support an allow_list field in its trigger_metadata. Any message content that matches an allow_list keyword will be ignored by the Auto Moderation KEYWORD rule. Each allow_list keyword can be a multi-word phrase and can contain wildcard symbols.
• Increase maximum number of rules with KEYWORD trigger_type per guild from 3 to 5
• Increase maximum length for each regex pattern in the regex_patterns trigger_metadata field from 75 to 260.

​

Upcoming Application Command Permission Changes

​

Types of command permission configurations

• Command-level permissions are set up by an admin for a specific command in their server. These permissions affect only a specific command.
• App-level permissions are set up by an admin for a specific app in their server. These permissions affect all commands for an app.
• default_member_permissions are set up by an app when creating or updating a command. default_member_permissions apply to that command in all servers (unless an override exists). More information about default_member_permissions is in the documentation.

​

What’s changing?

1. The logic used to apply permission configurations to a user in a given context within Discord clients
2. New APPLICATION_COMMAND_PERMISSIONS_V2 guild feature flag to indicate whether that guild is using the old permissions logic or the new (upcoming) logic.

​

1. How permission configurations are applied in Discord

Current behavior:

• If any command-level permissions are configured, all app-level permissions and default_member_permissions are ignored for that command.
• If any app-level permissions are configured, default_member_permissions is ignored for all of that app’s commands.

Upcoming behavior:

Flowchart for command permissions logic

​

2. APPLICATION_COMMAND_PERMISSIONS_V2 Guild Feature

• If the flag is present, that server is using the old command permissions behavior.
• If the flag is not present, that server has migrated from the old command permissions behavior to the new behavior.

​

Am I affected?

​

How do I prepare for the changes?

if 'APPLICATION_COMMAND_PERMISSIONS_V2' in guild.features:
     # Use current behaviors when interacting with endpoint
else:
     # Use new permissions behaviors when interacting with endpoint

​

What happens if I don’t update my app?

​

How long do I have to update my app?

​

GameSDK Feature Deprecation

• Achievements
• Applications
• Voice
• Images
• Lobbies
• Networking
• Relationships
• Storage
• Store

​

Add Auto Moderation Regex Support

​

Delete Ephemeral Messages

• DELETE /webhooks/<application_id>/<interaction_token>/messages/@original
• DELETE /webhooks/<application_id>/<interaction_token>/messages/<message_id>

​

New Select Menu Components

• User select (type 5)
• Role select (type 6)
• Mentionable (user and role) select (type 7)
• Channel select (type 8)

​

Default Sort Order for Forum Channels

​

Auto Moderation Spam and Mention Spam Trigger Types

• MENTION_SPAM blocks messages that mention more than a set number of unique server members or roles. Apps can define the number (up to 50) using the mention_total_limit field in the trigger metadata object when creating or updating an Auto Moderation rule.
• SPAM blocks links and messages that are identified as spam.

​

Forum Channels Release

​

Message Content is a Privileged Intent

​

If your app is verified

Temporary Message Content Intent

​

If your app is unverified

​

Slash Command Mentions

​

Session-specific Gateway Resume URLs

​

Upcoming Permissions Change to Webhook Routes

• GET /webhooks/{webhook.id}
• DELETE /webhooks/{webhook.id}
• PATCH /webhooks/{webhook.id}
• GET /channels/{channel.id}/webhooks
• POST /channels/{channel.id}/webhooks

​

Add Subcommand Groups and Subcommands to Message Interaction Objects

​

Upcoming Changes

​

Updating your app

​

Min and Max Length for Command Options

​

Calculated Permissions in Interaction Payloads

​

Changes to Bot Permissions for Interactions and Webhooks

​

Upcoming Changes

• When responding to an interaction (like application commands or message components)
• When executing a webhook that the bot created

​

Updating Your App

​

Message Content in Auto Moderation events

​

Updated Connection Property Field Names

​

Auto Moderation

• New endpoints for creating, updating, and deleting Auto Moderation rules
• New gateway events emitted when Auto Moderation rules are created (AUTO_MODERATION_RULE_CREATE), updated (AUTO_MODERATION_RULE_UPDATE ), and deleted (AUTO_MODERATION_RULE_DELETE ). Requires the AUTO_MODERATION_CONFIGURATION (1 << 20) intent
• New gateway event emitted when an action is executed (AUTO_MODERATION_ACTION_EXECUTION). Requires the AUTO_MODERATION_EXECUTION (1 << 21) intent
• New audit log entries when rules are created (AUTO_MODERATION_RULE_CREATE), updated (AUTO_MODERATION_RULE_UPDATE), or deleted (AUTO_MODERATION_RULE_DELETE), or when Auto Moderation performs an action (AUTO_MODERATION_BLOCK_MESSAGE)

​

Updated Command Permissions

​

Breaking changes

• Bearer tokens are now required to edit command permissions. Bearer tokens are tokens tied to an authenticating user’s permissions, and can be retrieved using OAuth. The user must have permission to manage the guild and roles.
• applications.commands.permissions.update scope was added as a requirement to edit command permissions.
• Disabled the batch editing endpoint (PUT /applications/{application.id}/guilds/{guild.id}/commands/permissions).

​

Other changes

• Created a CHANNEL command permission type
• Increase permission limit from 10 to 100
• constant (guild_id - 1) to represent all channels in command permissions
• Added default_member_permissions field, which is a bitwise OR-ed set of permissions, expressed as a string. This replaces the default_permission field, which will soon be deprecated.
• Added dm_permission, which is a boolean flag used to indicate whether a command is available in DMs (only for global application commands). If no value is passed, the global command will be visible in DMs.
• Added APPLICATION_COMMAND_PERMISSIONS_UPDATE gateway event and APPLICATION_COMMAND_PERMISSION_UPDATE audit log event.

​

Forum Channels

​

Guild Bans Pagination

​

API v10

• API v8 is now deprecated.
• GET /channels/{channel.id}/threads/active is decommissioned in favor of GET /guilds/{guild.id}/threads/active.
• Starting in v10, you must specify the message content intent (1 << 15) to receive content-related fields in message dispatches. Read more in the Gateway Intents documentation.
• To specify a reason for an administrative action in audit logs, apps must now pass the X-Audit-Log-Reason header rather than the reason parameter for all endpoints. Read more in the Audit Logs documentation.
• Message routes (like POST /channels/{channel.id}/messages) now use the embeds field (an array of embed objects) instead of embed.
• The summary field for applications now returns an empty string for all API versions.
• The name and description fields for Achievements are now strings, and localization info is now passed in new name_localizations and description_localizations dictionaries. This change standardizes localization to match Application Commands. Read details in the Achievements documentation.
• Existing attachments must be specified when PATCHing messages with new attachments. Any attachments not specified will be removed and replaced with the specified list
• Requests to v10 and higher will no longer be supported on discordapp.com (this does not affect dc.furballsnfts.live/_cdn)

​

Upcoming changes

• API v6 and v7 will be decommissioned in early 2023
• MESSAGE_CONTENT is becoming a privileged intent for verified bots in 75+ servers on August 31, 2022. Read details in the FAQ or follow the guide on updating your app.
• The summary field for applications will be removed in the next API version (v11)

​

Interaction Modals and Application Command Attachment Option Type

​

Guild Member Timeouts

​

Guild Scheduled Events

• Add official support for guild_scheduled_events field on Guild resource sent with GUILD_CREATE event

​

Nov 18, 2021

• Breaking change for return type for GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}/users
• Add with_user_count query param for GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}
• Return additional creator field by default in response for GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}
• More details and clarification for the guild scheduled events feature.
• Document support for before and after query params for GET /guilds/{guild.id}/scheduled-events/{guild_scheduled_event.id}/users

​

Nov 15, 2021

​

Application Command Autocomplete Interactions

​

Updated Thread Permissions

• “Use Public Threads” is now “Create Public Threads”, which allows users to create public threads and announcement threads in a channel, even if they cannot send messages in that channel.
• “Use Private Threads” is now “Create Private Threads”, which allows users to create private threads in a channel, even if they cannot send messages in that channel.

• “Send Messages in Threads”, which allows users to send a message in a thread. The “Send Messages” permission has no effect in threads: users must have “Send Messages in Threads” to send a message in a thread. This allows for setups where a user can participate in a thread but cannot send a message in the parent channel (like a thread on an announcement post).

​

User and Message Commands

​

Select Menu Components

​

Support for Multiple Embeds in Message Routes

​

Buttons and Message Components

• An optional components field has been added to the message object
• New response types 6 and 7 have been added for interaction responses, valid only for component-based interactions

​

API v9

​

Application Command Permissions

• GET Guild Application Command Permissions
• GET Application Command Permissions
• PUT Application Command Permissions

​

Large Bot Sharding Lowered to 150,000 Guilds

​

Changes to Slash Command Response Types and Flags

• Type 2 Acknowledge has been deprecated
• Type 3 ChannelMessage has been deprecated
• Type 5 AcknowledgeWithSource has been renamed to DeferredChannelMessageWithSource

​

Slash Commands in DMs

​

Change to Permission Checking when Creating Channels

​

Slash Commands and Interactions

• Webhooks can now update previously-sent messages from the same webhook using Edit Webhook Message and Delete Webhook Message

​

Inline Replies

• Inline replies are type 19 in v8, but remain type 0 in v6
• You can now add a message_reference on message create to create a reply
• A new field referenced_message has been added to the Message Object
• A new field replied_user has been added to the Allowed Mentions Object
• Message Create gateway event is guaranteed to have a referenced_message if the message created is a reply. Otherwise, that field is not guaranteed.

​

Stickers

​

Gateway v6 Intent Restrictions

​

API and Gateway V8

• API and Gateway v8 are now available. v6 is still the default for the time being.
• Gateway Intents are now required
• Removed guild_subscriptions in identify in favor of Gateway Intents.
• All permissions have been converted to strings-serialized numbers. As such, permissions_new, allow_new, and deny_new have been removed
• The game field has been removed. If you need a direct replacement, you can instead reference the first element of activities
• Channel Permission Overwrite types are now numbers (0 and 1) instead of strings (“role” and “member”). However due to a current technical constraint, they are string-serialized numbers in audit log options.
• embed_enabled and embed_channel_id have been removed. Use widget_enabled and widget_channel_id instead.
• Form body errors have been improved to include more helpful messaging on validation. See more here
• The Retry-After header value and retry_after body value is now based in seconds instead of milliseconds (e.g. 123 means 123 seconds)
• The X-RateLimit-Precision header is no longer respected. X-RateLimit-Reset and X-RateLimit-Reset-After are always returned at millisecond precision (e.g. 123.456 instead of 124)
• Bots no longer receive Channel Create Gateway Event for DMs
• delete-message-days is no longer available. Use delete_message_days.
• Removed roles, premium_since, and nick from Presence Update Gateway Event
• Removed some integration object fields for Discord application integrations
• Removed include_applications from Get Guild Integrations. Application integrations are always included.
• The following deprecated routes have been removed for better naming conventions:

• /guilds/<guild_id>/embed

• /servers/<guild_id>/embed.json
• /servers/<guild_id>/widget.json
• /guilds/<guild_id>/embed.json

• /guilds/<guild_id>/embed.png

• /channels/<channel_id>/messages/bulk_delete/

• /invite/<code>/

​

New Permission Fields

​

Legacy Mention Behavior Deprecation

​

New Properties on Guild Members Chunk Event

​

New Allowed Mentions Object

• Allowed mentions object

​

New Invite Events and Reactions Endpoint

• Delete All Reactions for Emoji
• Invite Create
• Invite Delete
• Message Reaction Remove Emoji

​

Rich Presence Spectate Approval

​

Gateway Intents

• Guild Create
• Request Guild Members
• Guild Member Add
• Guild Member Remove
• Guild Member Update
• Presence Update
• List Guild Members

​

IP Discovery Updates

​

GameSDK Version 2.5.6

​

GameSDK Version 2.5.5

​

Changes to Special Channels

​

More Precise Rate Limits

​

Bot Tokens for Achievements

​

Additional Team Information

​

Added Info Around Nitro Boosting Experiment

​

Deprecation of Discord-RPC Rich Presence SDK

​

New Invite Object Fields

​

Ask to Join & Rich Presence SDK

​

Documentation: Dispatch Store Listings

​

Enhancement: User Object

​

Documentation Fix: List of Open DMS in Certain Payloads

​

Deprecation: RPC online member count and members list

​

Enhancement: New Message Properties

​

Enhancement: Get Guild Emoji Endpoint

​

Deprecation: Accept Invite Endpoint

​

Semi-Breaking Change: Very Large Bot Sharding

​

New Feature: Rich Presence

• Showing more information about a user’s current game in their profile
• Allowing users to post invitations to join their party or spectate their game in chat
• Displaying “Spectate” and “Ask to Join” buttons on users’ profiles

​

Breaking Change: API & Gateway Below v6 Discontinued

​

New Feature: Channel Categories

​

New Feature: Emoji Endpoints

​

Breaking Change: Presence Activity Objects

​

Breaking Change: Default Channels

​

New Feature: Audit Logs

​

Breaking Change: Version 6

• Channel Object
  • is_private removed
  • type is now an integer
  • recipient is now recipients, an array of user objects
• Message Object
  • type added to support system messages
• Status Update Object
  • idle_since renamed to since