Discord APIBreaking changehigh
Discord stops listing channels bots cannot view in GET guild channels on Nov 16, 2026
- Detected
- Aug 26, 2026
- Effective
- Nov 16, 2026(today)
- Confidence
- 95%
What changed
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.
What to do
Audit your bot for any logic that reads channels it cannot view (e.g., full channel list mirroring, permission calculations across all channels). Handle the new CHANNEL_OBFUSCATED flag (1<<17) on channel.flags and treat application_id as nullable. Test Gateway obfuscation now by sending 1<<15 in your Identify capabilities or enabling the Developer Portal toggle. Prepare for HTTP omission on November 16, 2026.
Affected
endpoint: GET /guilds/{guild.id}/channelsendpoint: GET /users/@me/connectionsmodel: channel.flagsmodel: channel.application_idparam: CHANNEL_OBFUSCATED flag (1<<17)Source: discord.com (Discord's own page, checked by Breakwatch)
Is your code affected?
Search your repositories for the Discord SDK and the names above:
Or let Breakwatch do it: connect a repo and see which files call Discord, then get the next change as an alert pointing at those files. Check a repo free
Put it in your calendar: Discord deadlines (.ics) or every vendor's.