Discord

Multiple breaking changes detected in this changelog period, including: (1) Channel obfuscation for bots lacking VIEW_CHANNEL (channels hidden/omitted from HTTP responses starting Nov 16, 2026; Gateway behavior testable now), (2) `shard` param now required for Get Current User Guilds with large bot sharding (returns 400 without it), (3) `PRUNE_REQUIRES_ADMIN` guild feature requiring ADMINISTRATOR permission for prune endpoints, (4) `channel.application_id` is now nullable, and (5) Battle.net connections removed from Get Current User Connections as of Sept 22, 2026.

Multiple breaking changes are present in this diff, most critically: (1) Channel obfuscation for bots lacking VIEW_CHANNEL — channels will be hidden or have fields nulled over Gateway/HTTP; (2) `shard` param now required for large bot sharding on Get Current User Guilds; (3) `application_id` on channel object is now nullable; (4) Battle.net and Riot Games connections removed from Get Current User Connections; (5) PRUNE_REQUIRES_ADMIN guild feature adds new permission requirement for prune endpoints.

Multiple breaking changes were introduced across Discord's API: (1) GET /users/@me/guilds now returns 400 if `shard` param is omitted for large bot sharding apps; (2) `channel.application_id` is now nullable; (3) GET /guilds/{guild.id}/channels will omit channels where the bot lacks VIEW_CHANNEL starting November 16, 2026; (4) Guild prune endpoints now require ADMINISTRATOR permission if guild has PRUNE_REQUIRES_ADMIN feature; (5) Battle.net connections no longer returned by GET /users/@me/connections starting September 22, 2026.

Multiple breaking changes are present in this diff, most critically: (1) Channel obfuscation for bots on GET /guilds/{guild.id}/channels (effective November 16, 2026 for HTTP, testable now via Gateway), (2) 'shard' param now required for Get Current User Guilds for large bot sharding apps (returns 400 without it), (3) Battle.net connections removed from GET /users/@me/connections (fully effective September 22, 2026), (4) PRUNE_REQUIRES_ADMIN guild feature changes permission requirements for prune endpoints, and (5) channel.application_id is now nullable.

Multiple breaking changes detected in this diff, most critically: (1) Channel obfuscation for bots lacking VIEW_CHANNEL (Gateway changes active now, HTTP changes effective November 16, 2026); (2) shard param now required for Get Current User Guilds with large bot sharding (returns 400 without it); (3) Battle.net connections removed from Get Current User Connections starting September 22, 2026; (4) channel application_id is now nullable; (5) PRUNE_REQUIRES_ADMIN guild feature changes permission requirements for prune endpoints.

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

Multiple breaking changes announced: (1) Channel obfuscation for bots lacking VIEW_CHANNEL will hide sensitive channel fields over Gateway and omit channels from GET /guilds/{guild.id}/channels HTTP endpoint starting November 16, 2026; (2) Battle.net connections will no longer be returned by GET /users/@me/connections starting September 22, 2026; (3) Guild prune endpoints now require ADMINISTRATOR permission if guild has PRUNE_REQUIRES_ADMIN feature; (4) channel.application_id is now nullable; (5) Message forwarding now requires message content access.

Multiple breaking changes announced: (1) Channel obfuscation for bots lacking VIEW_CHANNEL — channels hidden via Gateway and omitted from HTTP GET /guilds/{id}/channels starting November 16, 2026; (2) Battle.net connections removed from GET /users/@me/connections immediately for new connections, and fully on September 22, 2026; (3) PRUNE_REQUIRES_ADMIN guild feature now gates prune endpoints behind ADMINISTRATOR permission; (4) channel.application_id is now nullable; (5) Message forwarding now requires message content access.

Discord is obfuscating channel data for bots that lack VIEW_CHANNEL permission: over the Gateway, sensitive fields will be nulled/replaced with '___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 stop being 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, sensitive channel fields will be nulled/replaced, and over HTTP, GET /guilds/{guild.id}/channels will omit inaccessible channels entirely starting November 16, 2026. Additionally, Battle.net connections will be removed from GET /users/@me/connections starting September 22, 2026, with no replacement.

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); over HTTP, GET /guilds/{guild.id}/channels will omit inaccessible channels entirely starting November 16, 2026. Bots that read full channel metadata regardless of their own access will be impacted.

Discord is introducing Channel Obfuscation for bots, where channels the bot lacks VIEW_CHANNEL permission on will have sensitive fields hidden over the Gateway (name becomes '___hidden___', fields nulled, new CHANNEL_OBFUSCATED flag set) and will be omitted entirely from GET /guilds/{guild.id}/channels HTTP responses. This is a breaking change effective August 12, 2026 for Gateway and November 16, 2026 for HTTP.

The `application_id` field on the Channel object is now nullable, meaning it can be serialized as `null` for future guild channels. This is a breaking change for apps or libraries that assume `application_id` is always a snowflake when present.

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 `application_id` is always a snowflake when present will break.

Starting July 10, 2026, Riot Games and League of Legends connections will no longer be returned by the GET /users/@me/connections endpoint. There is no replacement for this functionality.