Battle.net vs Tebex
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
Tebex
- HTTPS supported
- Requires X-Mashape-Key authentication
- No CORS support
| Feature | Battle.net | Tebex |
|---|---|---|
| Authentication | OAuth | X-Mashape-Key |
| HTTPS | Yes | Yes |
| CORS | Yes | No |
When to use which?
Battle.net works directly from the browser with CORS enabled, making it better for frontend-only apps.