The Battle.net API Deprecation: What Discord Developers Need to Know

Discord Just Broke an Old Battle.net Assumption

For developers building Discord integrations, small API changes can create surprisingly big problems.

Discord has deprecated the way developers could discover a user's Battle.net connection through the Get Current User Connections endpoint. New Battle.net connections stopped appearing through the endpoint earlier, and as of September 22, 2026, existing Battle.net connections stopped being returned as well. GitExtract

That means an integration that previously checked:

GET /users/@me/connections

and expected to find a battlenet connection can no longer rely on that behavior.

The important part is that Discord says there is no replacement for this functionality. GitExtract

For developers, this isn't simply a documentation update. It's a change to an assumption that may be buried inside account-linking, verification, profile, or game-related workflows.

What Exactly Changed?

The affected endpoint is Discord's Get Current User Connections API.

Historically, applications with the appropriate permissions could retrieve a user's connected services through:

GET /users/@me/connections

A Battle.net connection could appear in that list with a connection type such as:

battlenet

Discord's August 14 developer changelog announced that Battle.net connections were being deprecated from this endpoint. New connections were no longer returned, followed by the removal of existing connections on September 22. GitExtract

So the timeline is essentially:

August 14, 2026
Discord announces the deprecation.

Before September 22
New Battle.net connections are already excluded from the endpoint.

September 22, 2026
Existing Battle.net connections are also no longer returned.

Today
Developers should not depend on this endpoint to discover or verify Battle.net connections.

Why Did Discord Make the Change?

Discord's explanation is tied to its newer account-linking architecture.

The company says the new Battle.net connection is powered by Discord Social SDK and application identities. Because of that change, Battle.net connections are no longer exposed through the older user-connections endpoint. GitExtract

This fits into Discord's broader push toward deeper game integrations.

The Discord Social SDK has been expanding beyond basic Rich Presence into features such as account linking, unified social experiences, game profiles and other connections between games and Discord. Discord has also been rolling out application identities and new account-linking capabilities. Discord

So this isn't really about Battle.net disappearing from Discord.

It's about where that relationship lives and how developers are expected to interact with it.

Battle.net Is Still Connected. Your API Just Can't See It the Old Way.

This distinction is important.

A user can still have their Battle.net account connected to Discord for supported Discord functionality.

The API change affects developers that were using the old user connections endpoint to retrieve that relationship.

In other words:

User-facing connection:
Still possible for supported Discord experiences.

Old API lookup:
No longer available for Battle.net.

This can be confusing because developers may see a user's Battle.net connection in Discord while their API response doesn't contain it.

That isn't necessarily a broken account link.

It's the result of the API behavior changing.

What Could Break?

The impact depends on what your application was doing with the connection.

Battle.net account detection

If your application used:

GET /users/@me/connections

to determine whether someone had connected Battle.net, that check can no longer be treated as reliable.

Account verification

Some integrations may have used the existence of a Battle.net connection as a basic signal that a user had linked their gaming account.

That workflow needs to be reconsidered.

Profile or game features

If your application displayed Battle.net information based on the returned connection object, that information may now be missing.

Automated onboarding

Servers or applications that used Battle.net connections as part of onboarding or role assignment should review those flows carefully.

The biggest mistake would be assuming:

"The API returned no Battle.net connection, therefore the user isn't connected."

That conclusion is no longer valid.

What Developers Should Change

The first step is to search your codebase for every place where Battle.net is referenced.

Look for:

/users/@me/connections

and:

battlenet

Then check what your application actually does with that information.

If the logic looks something like:

Fetch user connections
        ↓
Find battlenet
        ↓
Verify Battle.net connection
        ↓
Unlock feature

that workflow needs to change.

The critical point is that Discord does not provide a replacement endpoint for this particular functionality. GitExtract

So developers shouldn't simply swap the old endpoint for another undocumented Discord API.

Don't Treat an Empty Response as a Failed Connection

This is probably the most important practical change.

Before the deprecation, an application could reasonably interpret the returned connection list as a source of information about the user's connected services.

Now, for Battle.net, an absent entry doesn't tell you that the user has no Battle.net connection.

It tells you that this API endpoint doesn't expose that connection anymore.

That difference matters if your application uses connection data for access control, account verification or game-specific features.

What About Discord Social SDK?

Discord's newer approach is increasingly centered around the Social SDK and application identities rather than treating every external game account as a generic connection returned by the old API.

Discord's Social SDK has continued receiving features around authentication, account linking, game identity and player-facing integrations. Discord

That doesn't mean every developer should immediately rebuild their application around Social SDK.

It means developers should understand that the old Connections API is no longer the universal source of truth it once appeared to be.

Especially for game integrations, Discord is moving toward more purpose-built systems.

A Bigger Lesson for Discord Developers

The Battle.net change is a good reminder not to build important application logic around assumptions about third-party connections.

APIs evolve.

A connection appearing in a Discord user's profile doesn't necessarily mean that the same connection will always be exposed through the same API endpoint.

For critical workflows, developers should:

• Track Discord's developer changelog.
• Avoid undocumented connection behavior.
• Keep third-party account verification separate from simple profile discovery.
• Review integrations whenever Discord changes its account-linking architecture.
• Avoid treating a missing connection as proof that an account isn't linked.

Discord specifically maintains a developer changelog for meaningful API and platform changes. Discord

What Happens Next?

For developers with Battle.net integrations, the immediate priority isn't finding a magical replacement endpoint.

There isn't one for this functionality according to Discord's deprecation notice. GitExtract

Instead, developers need to identify why they were reading the Battle.net connection in the first place.

If it was only being displayed, the feature may simply need to be removed or redesigned.

If it was being used for account verification, developers will need to rethink that verification flow using an appropriate supported account-linking or game integration mechanism.

And if the integration is built around Discord Social SDK, it's worth checking the latest SDK documentation and release notes rather than continuing to depend on the legacy Connections API. Discord

🎮 The Bottom Line

Discord's Battle.net API change is easy to miss because Battle.net isn't disappearing from Discord.

What's disappearing is the ability for developers to discover those connections through:

GET /users/@me/connections

New Battle.net connections were removed from the endpoint first, and existing connections followed on September 22, 2026. Discord says there is no replacement for that specific functionality. GitExtract

If your application relied on that endpoint, now is the time to audit the code rather than treating a missing battlenet entry as a failed account link.

Did your Discord integration rely on Battle.net connections through the old API? Let us know what you're changing in the comments.