Player information
v1.0.0This method retrieves player information
- Path: /info
- Request Method: POST
- Content-Type: application/json; charset=utf-8
- Headers: X-Art-Client-ID, X-Art-Client-TS, X-Art-Client-Signature
Request
| Parameter | Type | Description |
|---|---|---|
| user_id | string | Player ID on operator side |
| session_token | string | Token generated by provider for current game session |
| currency | string [currency enum] | Game currency. (currency code) |
Response
| Parameter | Type | Description |
|---|---|---|
| code | integer [enum] | Response code |
| message | string | Response any logical message |
| data | object | only needed when code 200 |
| user_id | string | ID of player on operator side |
| username | string | Name of player |
| balance | long | Current balance of player in specified currency. |
| currency | string [currency enum] | Currency of player |
| is_bonus_balanceoptional | boolean | Indicator if balance is bonus related. If value is false, aren't sent. |
Important!
Each request sent to the API requires validation using specific security headers. For details on implementing this, refer to Securing API Requests.
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