Getting started
Open Entertainment Platform offers API integration and hosted platforms. Explore products on the introduction page, manage apps and access applications under Applications, and view review results and account notifications in Inbox.
Choose an integration mode
| Mode | Suitable for | Prepare | Management |
|---|---|---|---|
| API integration | Teams maintaining their own site, players and wallet | Server, database, outbound IP and callback endpoint | Integration settings in this console; operations in your own system |
| Hosted platform | Merchants using shared infrastructure without separate deployment | Merchant name, company/team and contact details | Applications in this console; site and operations in the merchant dashboard |
Each app has one access application and approval flow. Creating an account or app does not grant access. Hosted merchants must also complete provisioning.
Hosted platform
- Create a developer account and select Create hosted merchant. Submit details and an access application.
- Wait for review. Provisioning starts automatically after approval.
- Once provisioning completes, open your merchant site or dashboard from app details.
- Configure your logo, unique access link or custom domain, and manage players and operations according to your permissions.
No server deployment or manual API credential management is required.
Read the hosted merchant guide
API integration: starter kit
The kit includes player accounts, game catalog and launch, wallet and unified callbacks.
- Download the kit and follow site/docs/deployment.md to deploy a separate site and database.
- Create an API app and apply for access with your server outbound IP and full callback URL.
- After approval, enter the endpoint, code and secret in the kit dashboard under Game integration settings.
- Use dedicated test players to verify games, callbacks, settlement and exit.
API integration: custom development
For teams with their own player system and wallet. Your server calls the APIs; the browser only opens the returned launch URL.
- Create an API app and apply for access.
- Implement server-side signed authentication and obtain a token.
- Query the game catalog and obtain a launch URL for the player.
- Implement unified callbacks and idempotency, then verify the integration.
Read the custom integration guide
Integration verification
Successful authentication and a visible game only confirm connectivity. Before opening to players, verify actual play, settlement, duplicate callbacks and abnormal exits. Persisted callbacks can be retried; a crash before queue persistence still requires manual reconciliation. See Callbacks and settlement.