Platform / Developers
Contracts first. Changelogs always.
Every operator-facing API is a versioned contract with documentation, generated clients and a public changelog. Breaking changes are refused by the build.
REST and OpenAPIWebhooksSandbox
curlTypeScriptGoKotlinC#operator API v1 · OpenAPI 3.1
# Read a player's limits
curl https://api.example-operator.com/v1/players/10482/limits \
-H "Authorization: Bearer $TOKEN" \
-H "Idempotency-Key: 7f3c...a91"
# 200 OK
{
"player_id": "10482",
"deposit_daily": { "amount": 200000, "currency": "ZAR", "used": 50000 },
"loss_weekly": { "amount": 250000, "currency": "ZAR", "used": 161000 },
"reality_check_minutes": 60,
"self_excluded": false
}
# Money is always integer minor units plus a currency.
Webhooks · live
player.status.changed200 · 84 ms wallet.balance.changed200 · 61 ms payment.withdrawal.heldretry 2 of 8 casino.round.settled200 · 47 ms
Changelog
v1.4.0 · added: loss limit history v1.3.0 · added: webhook replay endpoint v1.2.1 · fixed: pagination cursor docs Breaking changes: never within v1
Everything included
Everything for developers
What your integration team gets.
LaunchAfter launchRoadmap
APIs
- PAM: players, tags, limits, balances, bonuses
- Cashier: deposits, withdrawals, risk hooks
- Casino: game feed, launch, free spins, jackpots, statements
- Wallet seam for external wallets
- Reports API
- Sportsbook: bets and history
Conventions
- Money as integer minor units plus currency
- Idempotency keys on every write
- Cursor pagination and stable ids
- Errors with machine-readable codes
Events
- Webhooks with retries and replay
- Signed payloads
- Versioned event schemas with deprecation windows
Tooling
- OpenAPI documentation
- Clients generated in your build
- Public changelog per contract
- Sandbox per operator
- Provider integration and conformance kits
Reliability
- Per-operator rate limits and SLAs
- Status and SLOs per module
- Health checks and provider failover
Integrating with OpenStake?
Ask for sandbox access and the API documentation.