u/newtostew2

I’m working with Blizzard’s Battle.net WoW Profile API and I’m trying to determine whether the Protected Character Profile Summary is currently functional for MoP Classic.

I’ve narrowed it down pretty hard and I’m getting a consistent Retail/Classic split.

OAuth:

* Authorization Code flow * `wow.profile` scope * token introspection shows `ROLE_USER` * `IS_AUTHENTICATED_FULLY`

Using the same OAuth client and same freshly issued user token:

**Retail**

* public Character Profile Summary → `200` * `/profile/user/wow?namespace=profile-us` → `200` * Blizzard returns a `protected_character.href` * calling that exact Blizzard-provided href → `200`

**MoP Classic**

* public Character Profile Summary → `200` * `/profile/user/wow?namespace=profile-classic-us` → `200` * Blizzard returns a `protected_character.href` * calling that exact Blizzard-provided href → `403 BLZWEBAPI00000403 Forbidden`

The Classic URL is the exact `protected_character.href` returned by Blizzard’s Account Profile response. I’m deliberately not reconstructing the endpoint manually since I went over the 2025 bug thread and saw that had already been ruled out.

I also generated a completely fresh Authorization Code token and repeated the Classic test with the same result.

So at this point the same auth setup successfully completes the protected-character flow on Retail, while the equivalent Classic endpoint fails.

**Has anyone actually gotten a** `200` **from Protected Character Profile Summary on MoP Classic or another current Classic progression flavor?**

If so, I’d especially like to know:

* which namespace/flavor worked * whether you used anything beyond normal Authorization Code + `wow.profile` * whether there’s an undocumented Classic-specific requirement

Also, if this has already been figured out in the Blizzard API Community Discord, I’d greatly appreciate any info from that.

I’m specifically looking for a confirmed working example if one exists, since the identical client/token works against Retail protected-character.

Also, if anyone knows of any Blizzard API-team reply, update, or communication about this more recent than December 2025, I’d appreciate a link. That’s the newest official communication I’ve been able to find. You’d think there’d be *some* amount of community engagement beyond “we’re sorry we’ve been gone, we’ll work on it” with no follow-up..

I’m working with Blizzard’s Battle.net WoW Profile API and I’m trying to determine whether the Protected Character Profile Summary is currently functional for MoP Classic.

I’ve narrowed it down pretty hard and I’m getting a consistent Retail/Classic split.

OAuth:

• Authorization Code flow
• wow.profile scope
• token introspection shows ROLE_USER
• IS_AUTHENTICATED_FULLY

Using the same OAuth client and same freshly issued user token:

Retail

• public Character Profile Summary → 200
• /profile/user/wow?namespace=profile-us → 200
• Blizzard returns a protected_character.href
• calling that exact Blizzard-provided href → 200

MoP Classic

• public Character Profile Summary → 200
• /profile/user/wow?namespace=profile-classic-us → 200
• Blizzard returns a protected_character.href
• calling that exact Blizzard-provided href → 403 BLZWEBAPI00000403 Forbidden

The Classic URL is the exact protected_character.href returned by Blizzard’s Account Profile response. I’m deliberately not reconstructing the endpoint manually since I went over the 2025 bug thread and saw that had already been ruled out.

I also generated a completely fresh Authorization Code token and repeated the Classic test with the same result.

So at this point the same auth setup successfully completes the protected-character flow on Retail, while the equivalent Classic endpoint fails.

Has anyone actually gotten a 200 from Protected Character Profile Summary on MoP Classic or another current Classic progression flavor?

If so, I’d especially like to know:

• which namespace/flavor worked
• whether you used anything beyond normal Authorization Code + wow.profile
• whether there’s an undocumented Classic-specific requirement

Also, if this has already been figured out in the Blizzard API Community Discord, I’d greatly appreciate any info from that.

I’m specifically looking for a confirmed working example if one exists, since the identical client/token works against Retail protected-character.

Also, if anyone knows of any Blizzard API-team reply, update, or communication about this more recent than December 2025, I’d appreciate a link. That’s the newest official communication I’ve been able to find. You’d think there’d be some amount of community engagement beyond “we’re sorry we’ve been gone, we’ll work on it” with no follow-up..