Player Logout
This interface is called by downstream merchants when players log out or when user accounts are frozen. The gateway will update the local player status to Inactive (disabled) and send logout requests to each game provider to disconnect the player from all game lobbies.
API Information
| Property | Value |
|---|---|
| Path | POST /papi/v1/player/logout |
| Authentication | Agent Token (Bearer) |
| Content-Type | application/x-www-form-urlencoded |
Request Headers
| Header | Value | Required |
|---|---|---|
Authorization | Bearer {agent_token} | ✅ Yes |
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
member_id | string | Yes | The player's unique account identifier on the merchant side (automatically converted to uppercase) |
Request Example
bash
curl -X POST https://api.example.com/papi/v1/player/logout \
-H "Authorization: Bearer {agent_token}" \
-d "member_id=player_user_001"Response Fields
| Field | Type | Description |
|---|---|---|
code | int | Status code, 0 is success |
data | object | Response data (empty object) |
msg | string | Message |
Successful Response (HTTP 200)
json
{
"code": 0,
"data": {},
"msg": "logout success"
}Error Response
Player Not Found (HTTP 200)
json
{
"code": 7,
"data": {},
"msg": "player not found"
}Invalid Signature / Token (HTTP 200)
json
{
"code": 1002,
"data": {},
"msg": "err.signature.invalid"
}