The Player Information request is used for receiving information about the registered player. This request verifies the provided session token value on the Operator side.
In case of non-determined (unpredicted) HTTP server errors with HTTP Status Code 5xx (500, 501, 502, 503, 504, 505, 506, 507, 508, 509, 510, 511) from the wallet's side, the failed Player Information request will be retried maximum 10 times with pauses for a fixed period of time equal 1 second between attempts. If the last 10th attempt fails, the request will be rejected and the player will see an error.**
It is not possible to explicitly trigger the Player Information request retry via HTTP Status Code 200 and response code 501.
In case of connection issues with the wallet's server, the same retry method will be applied.
API Call Sample:
- Generated server url.http://integrator-gaming-platform.io/rest/v1/api/playerInformation
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
http://integrator-gaming-platform.io/rest/v1/api/playerInformation \
-H 'Content-Type: application/json' \
-d '{
"sessionToken": "0Ja8M7KvY",
"clientVersion": "1.0.0"
}'{ "code": "0", "description": "Success", "playerId": "3456", "playerName": "ninja", "currencyCode": "USD", "testPlayer": false }
Request Schema:
Login session token, provided by the Operator side. Used in all requests initiated by RubyPlay (the RGS) when invoking the Operator GP service.
Game Client version, provided by the our side (our Game Client).
Response Schema:
Response code.
Short description of the response code.
Unique player ID on the Operator side.
Unique player nickname on the Operator side.
Currency used by the current player.
Test players are not included in the billing report.