🔒 Gameball API V4.1 — Secure Integration Mode
We’re excited to announce API V4.1 — our most secure version yet, with mandatory SecretKey authentication and enhanced security controls!✨ What’s New
Mandatory SecretKey Authentication
All integration endpoints under/api/v4.1/integrations/... now require both APIKey and SecretKey headers. This ensures all integration traffic is server-to-server only.Enhanced Security Model
- All integration APIs must be called from your backend
- Widget/mobile access requires per-customer session tokens
- No exposure of SecretKey in client-side code
Minimum Version Enforcement
Control which API versions are allowed from your Gameball Dashboard. Set a minimum version to reject older, less secure patterns.🔄 Breaking Changes
📚 Migration Guide
Migration Required: If you’re using v4.0, you’ll need to update your integrations to include SecretKey headers and ensure all calls are made from your backend.
🚀 Gameball API V4.0 — A Major Upgrade
We’re thrilled to announce the release of API V4.0 — our most powerful, efficient, and developer-friendly version yet!✨ What’s New
RESTful Architecture
V4 follows best-practice RESTful principles with cleaner, more predictable routes that make integration smoother and more intuitive.Optimized Performance
Experience lightning-fast response times with streamlined request/response bodies that focus only on essential data.Enhanced Security
New secured endpoints protect sensitive customer data with Secret Key authentication, ensuring PII remains safe.Better Error Handling
Improved HTTP status codes and detailed error messages make debugging faster and easier.New Endpoints
- Get Customer Activities — Track detailed engagement logs
- Get All Customer Details (Secured) — Access full customer profiles safely
- Get/Update Coupon Configurations — Manage discount settings with ease
Batch Processing (Beta)
Process thousands of operations in a single API call — transform how you manage large volumes of data.🔄 Breaking Changes
Player → Customer: We’ve updated our terminology throughout the API. Update your integrations to use “Customer” instead of “Player.”
Ready to upgrade? Check out our V4 API Documentation and What’s New guide for complete details on all the exciting changes.