The game server uses this api to communicate with the partner's server. The game server executes a specified set of requests (currently it is 4 methods) to the partner's server. The partner needs to implement the processing of these requests and give the corresponding responses.****

Protocol

API.URI - don't forget to inform the manager of the address where you will handle requests.

Requests

1. The Platform executes all requests to APIs in POST(HTTP) format
2. The request URI is forming according to the scheme API.URI + '/' + serviceName + '.' + methodName
3. In the body of the request (http body) a string in JSON format is passed (object)
4. All requests will be signed using the Secret Key (unless otherwise specified for a particular method).

• The signature may be used by the Partner to verify that the request came from the Platform.
• Only the first level fields whose values are primitives (not objects) are involved in the request signature.
• The following partner, meta fields are not included in the signature.
• The meta  object is used to pass additional information that is not necessary for processing the request. For example, for slots the information about the number of lines, bet size, etc. is transmitted. The set and format of data in the meta field can change at any time and without warning, so it is not recommended to be tied to the processing of this data. If you need to receive static data on games (players, etc.), you should use the appropriate partner API or use login-password to access your personal cabinet.

Responses

1. The Partner must provide all responses in JSON format.

   • Http Status Code - is not part of API and all responses should have status 200 (in case of successful and unsuccessful calls (excluding transport layer errors)). Http Status Code different from 200 indicates either a serious problem on the server or a completely erroneous request.
   • General scheme for a positive answer : All positive answers must contain "status" in the body of the answer: 200

   {
         "status" : 200,
         "method" : "service.method",
         "response" : ...response entity as json...
   }
   

• The general pattern of the negative response:

  {      
  			"status" : "numeric code other than 200",
        "method" : "service.method",
        "message" : "String description of the error. For security reasons, the description does not necessarily clearly describe what happened on the server, but in some cases may serve as a hint. In other cases, contact technical support"
  }
  

Error processing

General Information:

• Connect timeout 1s
• Read timeout 3s