Verifying the Access
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| session_id | Yes | String | Specifies the session ID of the game accessed. |
| ticket | Yes | String | Specifies the ticket used for authentication. |
| auth_ts | Yes | String | Specifies the ticket validity period, in milliseconds. |
| encrypted_data | Yes | String | Specifies the internal encrypted data of SDK. |
| aes_iv | Yes | String | Specifies the internal encrypted salt value of SDK. |
Example Request
POST sign_check_url
{
"session_id": "xxxx",
"ticket": "xxxx",
"auth_ts": "128234892384", //Timestamp in milliseconds
"encypted_data": "", //Decrypt encypted_data to verify data validity based on aes_key and aes_iv and finally to improve access security.
"aes_iv": ""
} Response Parameters
| Parameter | Type | Description |
|---|---|---|
| request_id | String | Specifies the request ID, which is unique. |
| aes_key | String | Specifies the symmetric encrypted key. |
Example Response
{
"request_id": "6837531fd3f54550927b930180a706bf",
"aes_key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
} Last Article: Cloud Mobile Gaming Instance Event API
Next Article: Entering the Game Event
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.