API Reference
Beexar provides external APIs for operator integration, documented as interactive OpenAPI (Scalar) references where you can explore endpoints, models, and try requests. Game-launch endpoints are per integration platform (e.g. SoftSwiss) — an operator uses the launch API for its own integration_type.
Wallet API
Section titled “Wallet API”The Wallet API defines 4 HTTP endpoints that Beexar calls on the operator’s server during gameplay:
| Endpoint | Method | Description |
|---|---|---|
/balance | POST | Get player balance before showing the game UI |
/betwin | POST | Debit the bet and credit the win in a single atomic request |
/rollback | POST | Reverse previously confirmed transactions |
/finish | POST | Round completion signal (only when not closed by /betwin) |
All requests are signed with HMAC-SHA256 using the operator’s API secret (AUTH_TOKEN).
SoftSwiss Launch API
Section titled “SoftSwiss Launch API”Game launch is per integration platform. SoftSwiss-integrated operators call these endpoints to launch games:
| Endpoint | Method | Description |
|---|---|---|
/api/v1/softswiss/launcher/real | POST | Launch a real-money game session, returns launch_url |
/api/v1/softswiss/launcher/demo | POST | Launch a demo session with virtual balance |
All requests are signed with HMAC-SHA256 using the operator’s API secret (AUTH_TOKEN); demo sessions from the frontend send 64 zero characters. An operator may only call the endpoints for its own integration_type — calling another platform’s launcher returns 403 INTEGRATION_TYPE_MISMATCH.
Open SoftSwiss Launch API Reference →
Gateway API (base)
Section titled “Gateway API (base)”The base Gateway API is the platform-agnostic public surface:
| Endpoint | Method | Description |
|---|---|---|
/api/v1/operator/games | GET | List available games for an operator (public, no auth) |
/health | GET | Service health check |