The server on the operator side should be ready to receive API calls from the AGGREGATOR. Following is the list of API methods that should be implemented on the Operator for the AGGREGATOR.
All methods must be implemented to accept HTTP/HTTPS POST requests using the "application/json" format along with the parameters defined in each API request. The AGGREGATOR sends requests to the operator server and expects to receive a corresponding response.
- Login/Get Player Details API.
- Get Balance API.
- Debit/Bet API.
- Credit/Win API.
- Refund/Cancel API
5.1 Request and Response Format
- HTTP Header “Content-Type”: “application/json”
- Data sent in a POST request should be in JSON format.
- All the API responses are in JSON format.
- All Wallet API requests contain the "hash_key" request parameter which is used for security and validation. See the section titled Hash-Key Generation to learn more about how to generate and validate the "hash_key".
5.2 HASH-Key Generation
The Operator will be provided a shared secret-key at the time of integration which is used to
generate hash-key.
The hash key can be generated using the below steps:
- Generate a string by concatenating the values of specified parameters in corresponding
request. - Add the shared secret key at the end of the string.
- Generate MD5 hash using the resulting string as a hexadecimal representation.