Change Log

​

Developer Portal & Docs Refresh

​

Developer Portal

• New dev portal home page with quick access to apps, docs, and new developer videos.
• New theme with updated navigation and updated light/dark support.
• New Localization support! This will use the same language you have set in the Discord client.

​

Developer Docs

• Reorganized structure with new tabs for each feature area and new sidebars for easier navigation.
• New guides and overviews for platform-wide features and use cases, with more on the way!
• AI & MCP support: Docs now work with AI development tools via Copy-as-Markdown, an LLMs.txt file, and an MCP server, available at https://docs.discord.com/mcp
• Existing docs URLs are stable and were preserved during the reorganization. Some titles and content were updated or moved for clarity.

​

What’s Next

​

Discord Social SDK Release 1.8.14437

​

Security

• Filter the bearer token in all levels of logging
• Release builds only emit log statements for Error or Warning levels of severity
• Debug builds will still have logs for Info and Verbose levels of severity
• Added a DEBUG BUILD Warning at the top of the debug log that indicates it should not be used in production

​

Discord Social SDK Release 1.7.14433

​

Security

• Filter the bearer token in all levels of logging
• Release builds only emit log statements for Error or Warning levels of severity
• Debug builds will still have logs for Info and Verbose levels of severity
• Added a DEBUG BUILD Warning at the top of the debug log that indicates it should not be used in production

​

Discord Social SDK Release 1.6.14448

​

Security

• Filter the bearer token in all levels of logging
• Release builds only emit log statements for Error or Warning levels of severity
• Debug builds will still have logs for Info and Verbose levels of severity
• Added a DEBUG BUILD Warning at the top of the debug log that indicates it should not be used in production

​

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