Integration as Game Provider
This section provides detailed information and instructions for integrating as a games website or platform.
#1 Connection Parameters and Access Keys
To get access, it is necessary to contact the technical support of the platform. You will receive the following data:
| Name | Type | Description |
|---|---|---|
secret | string | a string for signature generation |
contentProviderId | string | a unique provider id, required to work with API accounts |
apiEndpoint | string | a link to the endpoint of interaction with the API |
testUserForProvider | object | |
testUserForProvider.authUrl | string | a link for the current state of the integration. Here you can test games launching, the passage of balance transactions and more |
Example:
{
"contentProviderId": "4b703f00-a7b5-4098-8fcc-bae9bbf2680e",
"secret": "JZwT5a22kW7bEYyb",
"apiEndpoint": "https://example.com/api-url/",
"testUserForProvider":
{
"authUrl": "https://example.com/test-user-auth"
}
}
#2 Creating Account
Within the framework of one connection, the provider can connect several lists of games with different restrictions and with commissions charged for different rates. This set of games with limitations is called account.
You can create them as follows:
- using API calls - see communications protocol;
- using the utility
sample-account-client/create-account.js, see using account creation utility.
#3 Loading Game List
To see the games in the lobby using the test link testSiteUrl, you need to upload them.
This can be done as follows:
- using API calls - see communications protocol;
- using the utility
sample-account-client/update-games.js, see using the game list download utility.
#4 Implementation of API for Processing Game Operations
For the integration to work correctly, all financial transactions are transferred to the platform server. See documentation on billing opperations
SDK contains an example of server implementation for node.js and a test html client. More details on the link SDK structure.