Discord APIBreaking changehigh
Discord makes six breaking bot API changes starting Aug 12, 2026
- Detected
- Sep 22, 2026
- Effective
- Aug 12, 2026(took effect 96 days ago)
- Confidence
- 97%
What changed
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) shard param 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_id on 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.
What to do
Audit all usages of GET /guilds/{guild.id}/channels for bots that read channels without VIEW_CHANNEL; add shard param to Get Current User Guilds if using large bot sharding; handle null application_id on channel objects; stop relying on Battle.net connections from GET /users/@me/connections; check PRUNE_REQUIRES_ADMIN feature before calling prune endpoints; ensure bots can read message content before forwarding.
Affected
endpoint: GET /guilds/{guild.id}/channelsendpoint: GET /users/@me/guildsendpoint: GET /users/@me/connectionsendpoint: GET /guilds/{guild.id}/pruneendpoint: POST /guilds/{guild.id}/prunemodel: channel.application_idmodel: channel.flagsparam: shardmodel: Presence Update activitiesendpoint: Message ForwardSource: 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