APIs & Integrations
Battlenet
Overview
Pre-built tooling
Pre-built use-cases
No pre-built use cases yet (time to contribute: <48h)
Not seeing the use case you need? Build your own independently.
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ❓ | |
Paid test account | ❓ | |
Partnership | ❓ | |
App review | ❓ | |
Security audit | ❓ |
Setup guide
No setup guide yet.
Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Useful links
Contribute useful links by editing this page
Connection configuration in Nango
-
Battlenet uses different domain extensions for different regions.
-
You need to pass the domain extension to use to Nango in the
nango.auth()
call:
-
For more details, see the docs here.
-
When creating a new connection, please provide your
apiDomain
. The API domain for Battle.net varies byregion
. For regions outside of China, the domain follows the format{region}.api.blizzard.com
, where{region}
can beus
,eu
,kr
, ortw
. For China, the API domain isgateway.battlenet.com.cn
.
API gotchas
- Tokens cannot be refreshed, hence when the token expires, resource owners will have to go through the authorize flow again.
Contribute API gotchas by editing this page