Discord APIBreaking changehigh

Discord changes channel, user and connection API fields on Aug 5, 2026

Detected
Aug 6, 2026
Effective
Aug 5, 2026(took effect 103 days ago)
Confidence
92%

What changed

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.

What to do

1) Update code that assumes application_id is always a non-null snowflake to handle null. 2) Remove any reliance on GET /users/@me/connections for Riot Games connection data — no replacement exists. 3) Apply for the identify.premium scope if Nitro subscription level is required. 4) Ensure your app has message content access before forwarding messages.

Affected

model: Channel.application_idendpoint: GET /users/@me/connectionsmodel: User.premium_typeendpoint: Message Forwardingparam: identify.premium scopemodel: Application.flags_newendpoint: PUT /lobbiesendpoint: POST /lobbies/{lobby.id}/messagesendpoint: GET /lobbies/{lobby.id}/messagesendpoint: PUT /channels/{channel.id}/voice-status

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:

npm: discord.jspip: discord.pypip: nextcordruby: discordrbgo: github.com/bwmarrin/discordgojava: net.dv8tion:JDAcsharp: Discord.Netrust: serenity

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

Get Discord API changes by email

Once a week: the breaking changes and upcoming deadlines for Discord, each linked to the vendor's own page. Free, no account. One-click unsubscribe.

More Discord API changes

Every Discord API change →