Game catalogue API
List, enable and disable titles from multiple studios through one endpoint group.
iGaming APIs
Connect game studios, manage player wallets and expose operator endpoints through LOOKME iGaming APIs. We supply integration infrastructure for licensed platforms — LOOKME does not operate casinos or betting brands.
Custom Solution
POST /v1/gaming/wallet/debit
Authorization: Bearer <api_key>
{
"player_id": "PLR_991",
"amount": 100,
"round_id": "RND_88"
}
200 OK
{ "balance": 2400, "status": "success" }
Licensed iGaming operators need a unified API layer to connect multiple game providers, manage player wallet balances, process debit/credit transactions and expose a consistent interface to their front-end application.
LOOKME provides game catalogue aggregation, provider API normalisation, wallet management endpoints, transaction logging and operator admin tools. Your platform team builds the player-facing experience; we power the integration backbone.
Clients must hold appropriate gambling licences for their target markets. LOOKME confirms jurisdictional scope during onboarding and does not support unlicensed or illegal gambling operations.
Representative REST routes issued after onboarding. Paths and fields may vary per project.
/v1/gaming/games
List enabled games from aggregated providers
/v1/gaming/session
Launch a game session for a player
/v1/gaming/wallet/debit
Debit player wallet for a game round
/v1/gaming/wallet/credit
Credit winnings or rollback a round
/v1/gaming/rounds/{id}
Reconcile round history and provider callbacks
Capabilities your engineering team integrates through REST endpoints and webhooks.
List, enable and disable titles from multiple studios through one endpoint group.
Start a player session and receive a provider launch URL or token.
Atomic balance changes tied to game rounds with rollback support.
Normalise different studio APIs behind consistent LOOKME contracts.
Fetch round history and match provider callbacks to internal ledgers.
Integrate odds or event feeds where the operator is licensed to use them.
Configure limits, currencies, maintenance windows and game visibility.
Alerts for unusual play patterns or provider-side incidents.
Signed HTTPS callbacks so your backend stays in sync without polling.
game.round_settled
Provider confirms round result and settlement
wallet.low_balance
Player balance below configured threshold
provider.maintenance
Studio or feed enters maintenance window
Typical steps from enquiry to live API access.
Confirm the client’s operating jurisdictions and which providers may be used.
Define wallet, session, callback and reporting contracts.
Implement against staging, then complete provider certification where required.
Admin training, monitoring and a documented support path.
Share your integration requirement, target markets and expected volumes. We will outline endpoints, webhooks and API access steps.