API Documentation

Authentication

v1.0.0

This is a method that consists in requesting an authentication for a player who is trying to launch the game

  • Path: /auth
  • Request Method: POST
  • Content-Type: application/json; charset=utf-8
  • Headers: X-Art-Client-ID, X-Art-Client-TS, X-Art-Client-Signature

Request

ParameterTypeDescription
user_tokenstringToken generated by operator during game launch process
session_tokenstringToken generated by provider for current game session
platformstring [platform enum]Enum: mobiledesktop
currencystring [currency enum]Game currency. (currency code)

Response

ParameterTypeDescription
codeinteger [enum]Response code
messagestringResponse any logical message
dataobjectonly needed when code 200
user_idstringID of player on operator side
usernamestringName of player
balancelongCurrent balance of player in specified currency.
currencystring [currency enum]Currency of player
is_bonus_balanceoptionalbooleanIndicator if balance is bonus related. If value is false, aren't sent.
maxbetoptionallongFor specific users (UK), the maxbet parameter in the auth request should be sent in units, consistent with how regular balance values are sent.

Important!

Each request sent to the API requires validation using specific security headers. For details on implementing this, refer to Securing API Requests.

Amount/Balance example

Amount/Balance fiat is represented in units(1$ = 1000 unit) and always is an integer value. For example: with 5.32 USD and the value will be 5.32 * 10^3 = 5320

Amount/Balance crypto is represented in units(1BTC = 100000000 unit) and always is an integer value. For example: with 0.0532 BTC and the value will be 0.0532 * 10^8 = 5320000

Possible codes

  • 200 - Success
  • 401 - User token is invalid
  • 403 - User token is expired
  • 413 - Invalid Client-Signature
  • 500 - Internal error

If code is 200 - operator should always return parameter data with information; HTTP status code should always be 200