Discord

Multiple breaking changes announced: (1) Channel obfuscation for bots lacking VIEW_CHANNEL permission rolls out on Nov 16, 2026 via HTTP and is testable now via Gateway; (2) Battle.net connections will be removed from GET /users/@me/connections starting September 22, 2026 with no replacement; (3) Channel application_id field is now nullable; (4) Prune endpoints now require ADMINISTRATOR permission for guilds with PRUNE_REQUIRES_ADMIN feature; (5) Message forwarding now requires message content access.

Multiple breaking changes announced: (1) Channel obfuscation for bots lacking VIEW_CHANNEL permission via Gateway and HTTP, effective November 16, 2026 for HTTP; (2) Battle.net connections removed from GET /users/@me/connections starting September 22, 2026; (3) PRUNE_REQUIRES_ADMIN guild feature adds new permission requirement for prune endpoints; (4) channel.application_id is now nullable.

Discord is introducing Channel Obfuscation for bots: over the Gateway, channels a bot lacks VIEW_CHANNEL on will have sensitive fields obfuscated (name becomes '___hidden___', other fields nulled/reduced, new CHANNEL_OBFUSCATED flag 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.

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.

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.

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_id` field is now nullable, which is a minor breaking change for code assuming it is always a snowflake when present.

The `application_id` field 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 the `GET /users/@me/connections` endpoint starting July 10, 2026, with no replacement.

The `application_id` field on the Channel object is now nullable, meaning it can be serialized as `null` for future guild channels. Apps or libraries that assume this field is always a snowflake when present must be updated to handle `null`.

Multiple breaking and deprecation changes were introduced, most notably: the `application_id` field 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_type` on the User object now returns 0 without the `identify.premium` scope, and message forwarding now requires message content access.