#
Description
- Notification of Match Status Change
Request Method
- HTTPS
- POST
- Parameters are in JSON format and placed in the body.
Request Parameters (New fields may be added, please ensure compatibility with newly added fields on the server side)
Parameter Name | Required | Type | Description | Example |
---|---|---|---|---|
notify_id | Yes | string | Notification ID | 0795d77f85789da0eb387a5096 |
notify_time | Yes | string | Server timestamp (in ms) | 1647834452408 |
app_id | Yes | string | ID of the application receiving the message | 1 |
notify_event | Yes | string | Notification event | sud.mg.merchant.match.status.changed |
data | Yes | MatchStatusChangedModel | Notification data | {} |
MatchStatusChangedModel
Parameter Name | Required | Type | Description | Example |
---|---|---|---|---|
group_id | Yes | string | Matching group ID | 14615640800525066 |
match_room_id | Optional (only when the matching status is successful) | string | Matching room ID (for subsequent game loading) | 146156408005250 |
status | Yes | string | Matching status, enumerated type MATCH_SUCCESS: Matching success MATCH_FAIL: Matching failure |
MATCH_SUCCESS |
Message Signature Verification
Request Example
{
"notify_id": "144884c98000100c-15da5e428a821000",
"notify_time": "1664266669547",
"app_id": "1461564080052506636",
"notify_event": "sud.mg.merchant.match.status.changed",
"data": {
"group_id": "g01",
"match_room_id": "m01",
"status": "MATCH_SUCCESS"
}
}
Notification Response
Parameter Name | Required | Type | Description | Example |
---|---|---|---|---|
ret_code | Yes | int32 | Return status code, 0 for successful notification, other error codes for failure | 0 |
ret_msg | Yes | string | Return message | SUCCESS |
Response Example
{
"ret_code": 0,
"ret_msg": "SUCCESS",
}