Battle.net vs Jservice
If you need a Games & Comics API that's easy to integrate, go with Battle.net.
Battle.net
Diablo III, Hearthstone, StarCraft II and World of Warcraft game data APIs
Battle.net
- HTTPS supported
- CORS enabled for frontend use
- Requires OAuth setup
Jservice
- No authentication required
- No HTTPS support
- Currently flagged as inactive
| Feature | Battle.net | Jservice |
|---|---|---|
| Authentication | OAuth | None |
| HTTPS | Yes | No |
| CORS | Yes | Unknown |
When to use which?
Jservice 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. Battle.net supports HTTPS, which is required for production deployments and secure data handling.