Battle.net vs Warface (non-official)
If you need a Games & Comics API that's easy to integrate, go with Warface (non-official).
Battle.net
Diablo III, Hearthstone, StarCraft II and World of Warcraft game data APIs
Warface (non-official)
Official API proxy with better data structure and more features
Battle.net
- HTTPS supported
- CORS enabled for frontend use
- Requires OAuth setup
Warface (non-official)
- No authentication required
- HTTPS supported
- No CORS support
| Feature | Battle.net | Warface (non-official) |
|---|---|---|
| Authentication | OAuth | None |
| HTTPS | Yes | Yes |
| CORS | Yes | No |
When to use which?
Warface (non-official) is the better choice for quick prototypes and hackathons since it requires no authentication. Battle.net works directly from the browser with CORS enabled, making it better for frontend-only apps.