Security
A secure launch API, isolated game runtime and operator-controlled wallet integration for B2B partners.
Integration
Integrate Okey through a signed server-to-server launch.
A secure launch API, isolated game runtime and operator-controlled wallet integration for B2B partners.
1
Credentials
Security
2
Integration
Rulesets
3
Webhooks
Integrations
4
Transactions
Reconciliation
API
Credentials
B2B platform · No player accounts or cashier services
POST https://api.okeyhan.com/api/v2/sessions/launch
x-okeyhan-api-key: {{sandbox_key_id}}
x-okeyhan-timestamp: 2026-08-09T12:34:56.000Z
x-okeyhan-nonce: {{unique_nonce}}
x-okeyhan-signature-version: 2
x-okeyhan-signature: {{hmac_v2}}
content-type: application/json
{
"operator_id": "{{operator_id}}",
"external_player_id": "{{opaque_player_id}}",
"display_name": "Alex",
"currency": "EUR",
"return_url": "https://casino.example/games",
"launch_request_id": "{{stable_logical_request_id}}"
}Environment
Production enablement is approval-gated.
API docs
Integrate Okey through a signed server-to-server launch.
How the casino-to-game integration works
The casino backend signs the launch; the browser receives only a short-lived URL; OKEYHAN runs the authoritative match and play-credit settlement.