Close
Operation executed by GPAS when closing a game. Some Operator Account Systems require this functionality. In the case of not being necessary it must be implemented anyway, returning fixed data.
Endpoint Details
Section titled “Endpoint Details”- Method: PATCH
- URL:
/sessions/close
Request Parameters
Section titled “Request Parameters”| Name | Type | Request | Description |
|---|---|---|---|
| id | String | QueryString | Wallet Session |
| x-parent-system-id | String | Header | Unique GPAS identifier in the operator system |
| x-signature | String | Header | Signature of the message for communication security, it must be in capital letters |
Request Example
Section titled “Request Example”PATCH /sessions/close?id=3fa85f64-5717-4562-b3fc-2c963f66afa6HEADERx-parent-system-id: BL13GTx-signature: SHA1(query string + secret key)Example Signature
Section titled “Example Signature”- QueryString:
id=3fa85f64-5717-4562-b3fc-2c963f66afa6 - SecretKey:
Ax34deSfgdB - SHA1: Encryption Function
- SHA1(
id=3fa85f64-5717-4562-b3fc-2c963f66afa6Ax34deSfgdB) - Signature:
097C11EEE445BB16C4FBC5197E1E4492BD47AB0F
Response Example
Section titled “Response Example”- HTTP Status Response
- Code: 200
- Description: Success
Implementation Notes
Section titled “Implementation Notes”- This method should close the wallet session identified by the
idparameter - After a session is closed, it should no longer be possible to perform operations using that session ID
- If the session ID is not found or is already closed, an appropriate error response should be returned
- Even if your system does not require explicit session closure, this method must still be implemented to maintain compatibility with GPAS
- A successful response should return HTTP status code 200 with no body content