Everything you need to get our full catalogue into your platform — IOP Originals and every aggregated studio on your plan, behind one integration.
Most operators go from credentials to a settling round in an afternoon. The full contracts live in the documentation.
Your apiKey and wallet webhookUrl live in the IOP backoffice under Integration → Config. One key per brand, server-side only.
Implement one wallet webhook with three actions — getBalance, processGameResult, rollback. We POST JSON, you reply in cents within 5 seconds.
One server call to /gw/launch with a gameId and player login returns a game_url. Originals, slots, live and sports through the same endpoint.
Run the verification scenarios, match your wallet ledger to the IOP transaction report, flip on aggregated providers, and you are live.
That is the entire integration. Everything else — currencies, limits, which games you carry — is configuration in your backoffice.
curl -X POST https://api.iop.global/gw/launch \ -H "Content-Type: application/json" \ -d '{ "apiKey": "YOUR_API_KEY", "gameId": "2", "login": "player-123", "currency": "USD", "country": "DE" }'
Read the complete reference, or hand the whole spec to a coding agent and let it write the integration for you.
Drop llms.txt into Claude, Cursor, ChatGPT or Windsurf and ask it to “implement this integration”. It carries the launch call, the full wallet contract, the money rules and every error case — a correct handler on the first pass.
Every endpoint, the complete wallet contract, error tables, the integration flow, verification tests, security and a changelog — all in one place.