Discord has released a series of significant updates to its developer platform, focusing on user safety, API efficiency, and privacy controls. These changes, detailed in the official Change Log, impact how bots, applications, and social SDK integrations interact with the platform. For developers building automation tools or community management bots, understanding these shifts is critical to maintaining compliance and functionality.
Age Assurance: New Runtime Behaviors
The most prominent update concerns the launch of Age Assurance. Discord emphasizes that for most developers, existing apps, bots, games, and social SDK integrations will continue to function without code changes. However, developers should be aware of four specific behaviors that may occur at runtime as these protections roll out.
First, regarding Bots and Apps, Private Profiles will now limit the visibility of custom statuses derived from user presence. This means bots relying on custom status data for user identification or context may encounter missing information for users with restricted privacy settings. Second, Activities that are age-restricted may require users to confirm their age group before access is granted. Third, in the realm of Commerce, parent-set spending limits may prevent certain purchases, which could affect in-app monetization strategies. Finally, for those using the Social SDK, Direct Messages (DMs) may be filtered into Message Requests more frequently, altering the user experience for new interactions.
For most developers, nothing changes: existing apps, bots, games, Activities, and Social SDK integrations continue to work as is.
Developers encountering unexpected issues related to these changes are advised to open a ticket with Developer Support. Full details are available in the Discord Help Center, ensuring that teams can adapt their error handling and user communication strategies accordingly.
Enhanced Invite Management via HTTP API
On September 18, 2026, Discord introduced new endpoints for managing invite target users, significantly improving the efficiency of user onboarding workflows. Previously, updating the target user list for an invite required uploading a CSV file, a process that was cumbersome for minor changes. The new target_user_ids parameter in the Create Channel Invite endpoint allows developers to pass an array of user IDs directly, eliminating the need for file uploads for initial setup.
Furthermore, four new endpoints have been added to the Update Target Users functionality. These include Add Target User and Remove Target User for single-user modifications, as well as Bulk-Add Target Users and Bulk-Delete Target Users for managing multiple users via a user_ids array of snowflakes. These endpoints adjust the list in place, replacing the previous asynchronous job processing for CSV files. All these operations require the caller to be the inviter or possess the MANAGE_GUILD permission, ensuring security and proper authorization.
Privacy Controls and Gateway Updates
Effective September 17, 2026, Discord has refined how custom statuses are handled through the Gateway. If a user’s Profile Privacy Setting is set to "Friends Only" or "Friends & Small Servers Only" in a guild with more than 200 members, their custom status (activity type 4) will be omitted from the activities field of Presence Update events. This change applies to all apps and bots subscribed to the guild’s presence.
It is important to note that other activity types, such as Playing, Streaming, Listening, Watching, and Competing, are not affected by this specific privacy setting. However, these may still be controlled by separate Activity Sharing settings. Developers building presence-based bots should update their logic to account for potential missing custom status data, ensuring that their automation tools do not fail or behave unexpectedly when this data is unavailable.
Best Practices for Account Unlinking
Discord has also published a new guide titled "Unlinking Accounts," aimed at developers using the Discord Social SDK. This guide outlines best practices for unlinking a user’s Discord account from a game or application. A key recommendation is to always revoke a user’s access and refresh tokens upon unlinking, rather than simply removing the local record. Failing to do so can lead to relinking conflicts and security vulnerabilities.
The guide also addresses how to handle out-of-band unlinks using the APPLICATION_DEAUTHORIZED webhook event. This ensures that developers can react promptly when a user manually unlinks their account through Discord’s settings, maintaining data integrity and security across the ecosystem.
Conclusion
These updates reflect Discord’s ongoing commitment to balancing developer capabilities with user safety and privacy. While the Age Assurance changes primarily affect runtime behavior rather than code structure, the new invite endpoints offer substantial improvements for automation and user management. Developers are encouraged to review the full Change Log and associated documentation to ensure their bots and applications remain compliant and efficient. As the platform evolves, staying informed about these granular API and privacy changes will be essential for building robust and user-friendly Discord integrations.