Regionality and Partitions


Important: You must update your integration by January 6, 2019.

We have launched a new Developer Portal to enhance our offering to community developers. In order to maintain service, please read our migration guide.


Managing accounts & games across the globe can be a daunting task, and Blizzard has created several concepts to help deliver epic experiences to all customers.  As a user of our APIs, it's helpful to understand how data is separated in order to provide a good experience for your customers, too.

The first element to understand is user account partitions. Blizzard operates two main account partitions, one in CN, the other across the globe.  In all situations where documentation mentions that something is unique, this is within a particular partition.  One major example of this would be account IDs.  An account ID is unique within a partition, but IDs across partitions could be duplicated.

Partition Regions
China CN
Worldwide US, EU, KR, TW, SEA


The second element to be concerned with are regions.  A region is typically a cluster of data centers, where most game data is held, and user accounts are homed.  Specifically in regards to game information, data from region to region can and will be different.  For instance, a user can have both a US WoW account and an EU one, where each region will have different characters, achievements and other information.  Likewise, a D3 user may have a single license for D3 on their account, but the character list for each region the game operates in will be different.

US, WoW, D3, SC2
EU, WoW, D3, SC2
KR, WoW, D3, SC2
TW, WoW, D3, SC2
CN, WoW, D3, SC2


For optimal user experience, you will want to use the region closest to the user for retrieving account data. You may need to game data request multiple regions for data if the user indicates that they play in multiple regions.