Discord APIBreaking changehigh
Discord stops listing channels bots cannot view in GET guild channels on Nov 16, 2026
- Detected
- Aug 15, 2026
- Effective
- Nov 16, 2026(today)
- Confidence
- 97%
What changed
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.
What to do
Audit any bot logic that reads channels it may not have VIEW_CHANNEL permission for (e.g., full channel list mirroring, permission auditing, channel structure reporting). Use the CHANNEL_OBFUSCATED flag (1 << 17) to detect obfuscated channels. Test Gateway behavior now by sending capability 1 << 15 in the Identify payload or enabling the 'Private Channel Obfuscation' toggle in the Developer Portal. Update code to handle application_id as nullable on channel objects.
Affected
endpoint: GET /guilds/{guild.id}/channelsmodel: Channel Objectparam: application_idparam: flags (CHANNEL_OBFUSCATED 1 << 17)param: permission_overwritesheader: Gateway CHANNEL_UPDATE eventSource: 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.