Discord API changelog
Breaking changes, deprecations and new features in the Discord API, read from Discord's own changelog and docs every few hours and classified by severity. Latest breaking change or deprecation: Sep 22, 2026.
Monitored sources:
SDK packages:
Last change seen on a source: Nov 17, 2026
Get Discord API changes by email
Once a week: the breaking changes and upcoming deadlines for Discord, each linked to the vendor's own page. Free, no account. One-click unsubscribe.
Change history
- New featureinfoDiscord adds four new endpoints for guild and channel member/role permissions
Discord added four new HTTP API endpoints to retrieve member or role permissions for guilds and channels. The channel endpoints apply implicit permission masking by default, which can be disabled with
implicit=false.Oct 31, 2026
Effective Oct 30, 2026
- Behavior changemediumDiscord removes implicit SET_VOICE_CHANNEL_STATUS denial when CONNECT is denied on Oct 29 2026
Discord clarified that users already connected to a voice channel can set the channel's status via SET_VOICE_CHANNEL_STATUS even without the CONNECT permission. Previously, a denied CONNECT implicitly stripped SET_VOICE_CHANNEL_STATUS; this implicit behavior is now removed.
Oct 30, 2026
Effective Oct 29, 2026
- New featureinfoDiscord adds content scanning flags for attachments embeds and media on Oct 28 2026
Discord has documented content scanning flags that are set on attachments, embeds, and media components when its scanner detects explicit, gore, or self-harm content. Apps can now read these flags to inspect media before acting on it, such as reposting to another channel.
Oct 29, 2026
Effective Oct 28, 2026
- Breaking changehighDiscord makes six breaking bot API changes starting Aug 12, 2026
Multiple breaking changes are present in this diff, most notably: (1) Channel obfuscation for bots lacking VIEW_CHANNEL (Gateway obfuscation now testable, HTTP enforcement on Nov 16 2026); (2)
shardparam now required for Get Current User Guilds with large bot sharding; (3) Battle.net connections removed from Get Current User Connections starting Sep 22 2026; (4)application_idon channel object is now nullable; (5) PRUNE_REQUIRES_ADMIN guild feature changes permission requirements for prune endpoints; (6) Message forwarding now requires message content access.Sep 22, 2026
Effective Aug 12, 2026
- Breaking changehighDiscord stops listing channels bots cannot view in GET guild channels on Nov 16, 2026
Discord is obfuscating channels that bots lack VIEW_CHANNEL permission on: over the Gateway, sensitive fields will be hidden and a new CHANNEL_OBFUSCATED flag (1<<17) will be set; over HTTP, GET /guilds/{guild.id}/channels will omit those channels entirely starting November 16, 2026. Additionally, the channel object's application_id field is now nullable, and Battle.net connections will no longer be returned by GET /users/@me/connections starting September 22, 2026.
Aug 26, 2026
Effective Nov 16, 2026
- Breaking changehighDiscord stops listing channels bots cannot view in GET guild channels on Nov 16, 2026
Discord is obfuscating channel data for bots that lack VIEW_CHANNEL permission. Over the Gateway, hidden channels will have sensitive fields replaced with placeholder values and a new CHANNEL_OBFUSCATED flag; over HTTP, GET /guilds/{guild.id}/channels will omit those channels entirely starting November 16, 2026.
Aug 22, 2026
Effective Nov 16, 2026
- Breaking changehighDiscord stops listing channels bots cannot view in GET guild channels on Nov 16, 2026
Discord is changing channel visibility for bots: over the Gateway, channels a bot lacks VIEW_CHANNEL on will have sensitive fields obfuscated (name becomes '___hidden___', new CHANNEL_OBFUSCATED flag set), and over HTTP, GET /guilds/{guild.id}/channels will omit inaccessible channels entirely starting November 16, 2026. Additionally, the channel object's
application_idfield is now nullable, which is a minor breaking change for code assuming it is always a snowflake when present.Aug 15, 2026
Effective Nov 16, 2026
- Breaking changehighDiscord ends Riot connections Jul 10, 2026, application_id now nullable
The
application_idfield on the Channel object is now nullable for future guild channels, which is a breaking change for apps or libraries that assume the field is always a snowflake when present. Additionally, Riot Games connections are no longer returned by theGET /users/@me/connectionsendpoint starting July 10, 2026, with no replacement.Aug 14, 2026
Effective Jul 10, 2026
- Breaking changehighDiscord makes Channel application_id nullable on Aug 5, 2026
The
application_idfield on the Channel object is now nullable, meaning it can be serialized asnullfor future guild channels. Apps or libraries that assume this field is always a snowflake when present must be updated to handlenull.Aug 12, 2026
Effective Aug 5, 2026
- Breaking changehighDiscord changes channel, user and connection API fields on Aug 5, 2026
Multiple breaking and deprecation changes were introduced, most notably: the
application_idfield on the Channel object is now nullable (previously always a snowflake when present), Riot Games connections are no longer returned by GET /users/@me/connections,premium_typeon the User object now returns 0 without theidentify.premiumscope, and message forwarding now requires message content access.Aug 6, 2026
Effective Aug 5, 2026
See which of your files call Discord
Connect a GitHub repo and Breakwatch maps your Discord usage, then alerts you when a change touches it, pointing at the exact files. Free for 1 repo.
Check a repo free