API Documentation

Your client server talks to our platform, and our platform talks to the main provider. All provider credentials stay server-side. You only need your API Key and API Secret from your client panel.

1. Base URL
2. Authentication
3. Launch Service URL
4. Balance Endpoint
5. Provider Callback URL (for main provider dashboard)
6. Client Callback (Platform → Client)

1. Base URL

https://omnigaming.online/api/

2. Authentication

Send your API Key and API Secret in every request. We support headers or query parameters, but headers are recommended.

X-API-Key: your_api_key
X-API-Secret: your_api_secret

3. Launch Service URL

POST /api/launch

Generate a whitelabeled game launch URL. We map your internal player ID to a provider-safe member account server-side.

Request

{
  "member_account": "player_001",
  "game_uid": "JILI_SLOT_001",
  "balance": 500.00,
  "home_url": "https://your-site.com"
}

member_account — your internal player ID. We map it to a provider-safe member account server-side so each player can be tracked separately.
game_uid — the game identifier from our services list.
balance — current player balance for the session (optional; falls back to the player's last known balance).
home_url — URL to return player after game session.

Your internal player ID is never sent to the provider. The platform generates a unique provider member account per player in the format c{client_id}_{your_player_id}.

Response

{
  "code": 0,
  "msg": "Success",
  "payload": {
    "game_launch_url": "https://omnigaming.online/play.php?t=LAUNCH_TOKEN_XYZ"
  }
}

4. Balance Endpoint

GET /api/balance

Check your current available GGR balance.

Response

{
  "code": 0,
  "msg": "Success",
  "balance": 1250.50,
  "currency": "BDT"
}

5. Provider Callback URL

Configure this callback URL in your main provider dashboard:

https://omnigaming.online/api/callback.php

We receive provider wallet events, verify the X-Signature using HMAC-SHA256, update GGR balances and then optionally forward to your own callback URL.

Provider Payload Example

{
  "serial_number": "uuid-txn-id-1234",
  "currency": "BDT",
  "game_uid": "JILI_SLOT_001",
  "member_account": "c1_player_001",
  "win_amount": "150.00",
  "bet_amount": "100.00",
  "timestamp": "1631459081871",
  "game_round": "round_id_555",
  "data": null
}

The member_account is the provider-safe value generated by the platform during launch (format c{client_id}_{player_id}). The platform decodes it to identify the correct client and player.

Platform Response

{
  "code": 0,
  "msg": "Success",
  "balance": 550.00
}

The balance returned is the updated player balance after applying win/bet amounts. GGR charges are tracked separately in the client wallet.

6. Client Callback (Platform → Client)

You can set your own callback URL in the client settings. We forward the wallet event to your URL, replacing the provider member_account with your original internal player ID and adding the updated balance, net_loss and GGR details.

You can also whitelist callback IPs and domains (comma separated) for extra security.