WoW: Forever API notes

What the Blizzard Battle.net API returns for World of Warcraft: Forever. Last checked 2026-10-31 22:45 UTC.

Short version

So right now you can list the realms, read most of the game data, and see your own characters through the account profile. Looking up characters and guilds by name doesn't work yet.

Making a request

Nothing special. Get an app token with the client credentials flow and pass the Forever namespace. The hosts are the normal regional ones.

curl -u "$CLIENT_ID:$CLIENT_SECRET" -d grant_type=client_credentials https://oauth.battle.net/token

curl -H "Authorization: Bearer $TOKEN" \
  "https://eu.api.blizzard.com/data/wow/realm/index?namespace=dynamic-forever-eu&locale=en_GB"

Namespaces follow the usual pattern: dynamic-forever-eu, dynamic-forever-us, profile-forever-eu and so on. The static one is the exception, it carries a build number: static-1.60.1_70399-forever-eu (same for us and tw). 70399 is not the client build (70707), so expect it to change with patches. The account profile links to it, which is the easiest way to find the current one. The response header battlenet-namespace echoes the one you used.

Other headers worth knowing: battlenet-schema names the document type (realm, revision 1), and cache-control: max-age=86400 means a response may be cached for a day. Every document currently has the same last-modified: Oct 30, 23:46:51 GMT. Nothing has changed since.

403 or 404?

This is how you tell what's open. On an existing route, a namespace that doesn't exist (try dynamic-bogus-eu) gives 403. A namespace that exists but has nothing at that path gives 404. That's how we know profile-forever is live: an unknown character returns 404, the same request with a made up namespace returns 403.

One catch: a route that doesn't exist at all is a 404 in any namespace, closed or not. /data/wow/hardcore/index on static-forever is a 404, not a 403.

The static namespace only answers to its exact versioned name. static-forever-eu and static-1.60.1_70707-forever-eu (the client build) are both 403.

Regions

CAMWOW looks like Blizzard's internal name for Forever. It's in every region and realm name.

Realms and rulesets

Forever doesn't show realms to players, you pick a ruleset instead. Behind that are normal realms, and the API lists them. The ruleset is the realm's type:

Counts are game realms only. The lists also contain service entries (Web, GMSS, Partner, Account, Log, CSI) that are clearly not for players. They're greyed out below. EU realms report enGB and Europe/Paris, US and AU realms enUS and America/Chicago, TW realms zhTW and Asia/Taipei.

The realm document looks like this:

GET /data/wow/realm/camwow-eu4-realm-3-pve?namespace=dynamic-forever-eu

{
  "id": 6937,
  "region": { "name": "CAMWOW Europe", "id": 93 },
  "connected_realm": { "href": ".../data/wow/connected-realm/6937?namespace=dynamic-forever-eu" },
  "name": "CAMWOW EU4 Realm 3 PvE",
  "category": "English",
  "locale": "enGB",
  "timezone": "Europe/Paris",
  "type": { "type": "NORMAL", "name": "Normal" },
  "is_tournament": false,
  "slug": "camwow-eu4-realm-3-pve"
}

Endpoints

We tried every route from the retail Game Data and Profile docs, about 107 in total, plus every link the open documents point to. Same result on eu and us. Here's what matters:

The 404s on connected realms are worth watching. Every realm links to its connected realm, but those links don't resolve yet. Auctions hang off connected realms, so the auction house won't be there until they do.

Characters and guilds

Thanks to Makkybis for the tip that the account profile works. It needs a user token: the authorization code flow with scope wow.profile, so the player logs in with their own Battle.net account. Your app needs a registered redirect URL for that.

GET /profile/user/wow?namespace=profile-forever-eu   (user token)

"wow_accounts": [{
  "id": 1234567,
  "characters": [{
    "character": { "href": ".../profile/wow/character/davina-asaria?namespace=profile-forever-eu" },
    "protected_character": { "href": ".../profile/user/wow/protected-character/6855-716333?namespace=profile-forever-eu" },
    "name": "Davina",
    "surname": "Asaria",
    "id": 716333,
    "playable_class": { "name": "Priest", "id": 5 },
    "playable_race": { "name": "Troll", "id": 8 },
    "gender": { "type": "FEMALE", "name": "Female" },
    "faction": { "type": "HORDE", "name": "Horde" },
    "level": 1
  }]
}]

What this tells us:

• Surname. name is the first name, surname is a new field. Retail and Classic characters on the same account don't have it.
• No realm field. Retail characters in the account profile have a realm object, Forever characters don't. The realm only shows up in the protected character link: 6855-716333 is realm id and character id. Realm 6855 is camwow-eu5-realm-1-pve, one of the Normal (PvE) realms. A Skyborne warrior on the same account sits on the same realm.
• Character URLs without a realm. The character link is /profile/wow/character/davina-asaria: first name and surname, no realm slug. That fits Forever names being unique per region. Right now it's a 404, and so is /profile/wow/character/camwow-eu5-realm-1-pve/davina-asaria. Maybe level 1 characters aren't published (retail doesn't show characters below level 10 either), maybe it just isn't switched on yet.
• Logging out updates it. Characters created through the Name Register only showed up after logging into the game, opening the character list and logging out again. Before that the account profile was a 404 in every region.
• 404 means no characters. An account without Forever characters gets a 404, not an empty list. Classic Era does the same for an account without Era characters.

Guilds are still a 404 everywhere. We also tried a dozen staff and test names on the GM, Partner and Web realms in EU and US. Nothing.

The version server

Not part of the Battle.net API, but public and useful. https://us.version.battle.net/v2/products/wowf/versions is what the launcher asks for. Forever is product wowf:

Region | BuildId | VersionsName
us     | 70707   | 1.60.1.70707
eu     | 70707   | 1.60.1.70707
cn     | 70707   | 1.60.1.70707
kr     | 70707   | 1.60.1.70707
tw     | 70707   | 1.60.1.70707

So the client is ready for all five regions, including China (downloads through NetEase's CDN) and Korea, even though the Korean API is still closed. The build config calls it WOW-70707patch1.60.1_Retail.

Other products on the same server run Forever builds (1.60.x) too:

A higher build on wowdev2 or wownev12 than on wowf is the earliest sign of a patch. At the time of writing nothing newer than the launch build is staged.

The product config (from the CDN, linked in the versions file) has a few facts the launcher uses:

• 10 languages: enUS, deDE, esES, esMX, frFR, ruRU, koKR, ptBR, zhTW, zhCN. No Italian.
• Minimum spec: 4 cores at 3 GHz, 8 GB RAM, 64 bit, Windows 10 1903 or macOS 12.
• There's a Wow-arm64.exe, so it runs natively on Windows on ARM.
• It installs into the shared World of Warcraft folder, subfolder _forever_. Multiboxing is allowed, offline play isn't.

The official website

The armory and realm status pages on worldofwarcraft.blizzard.com use a game version key in the URL, for example /en-gb/worldsoul/eu/armory/character/... for retail. The keys the site knows right now are modern, classic1x, classicann and classic. Forever isn't one of them: /en-gb/forever/eu/server-status is the same generic page you get for a made up key, and the armory under /forever/ is a 404. Expect a new key there once Forever gets its armory.

The status page loads its data from /graphql, but that endpoint only takes the site's own safelisted queries. Not usable from outside.

Not tested

• The China API, which needs a separate developer account.