This call is normally made before any other calls using the token sent on the game launch. It is used
to retrieve the player details from the Operator.
6.1 Login Request
| Type | Input |
| Method | POST |
| URL | https://<OPERATOR-BASE-URL>/login |
| Headers | "Content-Type": "application/json" |
| POST Parameters | JSON Object |
| Example | { "session_id": "0b3fcbee-9c1e-4c8b-b97a-8d1746a8a96a", "hash_key": "abcd-efgh-1234" } |
6.2 Request Parameters
| Parameter | Type | Description | Optional |
| session_id | String | Token received from game launch request | |
| hash_key | String | The computed md5().hex digest() value of (session_id+ secret key) |
6.3 Response Parameters
| Parameter | Type | Description |
| username | String | Player unique identifier |
| currency | String | The 3-letter ISO 4217 currency code of the player |
| account_id | String | Player Account ID |
6.4 Example Login Response
{
"username": "srinivas",
"currency": "USD",
"account_id": "123"
}
6.5 Example Error Response
The error response indicates a hash validation failure (code 5011) with the message "InvalidHash"
providing details about the unsuccessful hash validation process. Refer to section 12 for more
information.
{
"error": true,
"code": 5011,
"message": "InvalidHash",
"detail": "Hash Validation failed”
}