Discord APIBreaking changehigh

Discord ends Riot connections Jul 10, 2026, application_id now nullable

Detected
Aug 14, 2026
Effective
Jul 10, 2026(took effect 129 days ago)
Confidence
95%

What changed

The application_id field on the Channel object is now nullable for future guild channels, which is a breaking change for apps or libraries that assume the field is always a snowflake when present. Additionally, Riot Games connections are no longer returned by the GET /users/@me/connections endpoint starting July 10, 2026, with no replacement.

What to do

Update any code that reads channel.application_id to handle null values. For Riot Games connections, remove any logic that relies on GET /users/@me/connections returning Riot or League of Legends connection data, as there is no replacement.

Affected

model: Channel.application_idendpoint: GET /users/@me/connections

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 →