#

SUD

Description

  • Bullet Screen - Client Closed

Request Method

  • https
  • POST
  • Parameters are in JSON format and placed in the body

Request Parameters (Additional fields may be added, please keep compatibility with the 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-side timestamp (milliseconds) when the notification was sent 1647834452408
app_id Yes string Application ID of the message recipient 1
notify_event Yes string Notification event sud.mg.merchant.bullet.client.closed
data Yes BulletClientClosedModel Notification data {}
BulletClientClosedModel
Parameter Name Required Type Description Example
mg_id Yes string Game ID 14615640800525066
anchor_id Yes string Anchor ID 9009
msg_id Yes string Message ID 1692082187609964545
timestamp Yes int64 Millisecond timestamp 1692258830045
Message Signature Verification

Signature Verification

Request Example

{
    "notify_id": "0795d77f85789da0eb387a50964993a3eba1fedfec2b12f729861392a9b5ad04",
    "notify_time": "1647844976502",
    "app_id": "14615640800525066",
    "notify_event": "sud.mg.merchant.bullet.client.closed",
    "data": {
        "mg_id": "mgid01",
        "anchor_id": "9009",
        "msg_id": "1692082187609964545",
        "timestamp": 1692258830045
    }
}

Notification Response

Parameter Name Required Type Description Example
ret_code Yes int32 Return status code, 0 means message notification successful, other error codes mean failure 0
ret_msg Yes string Return message SUCCESS

Response Example

{
    "ret_code": 0,
    "ret_msg": "SUCCESS",
}

results matching ""

    No results matching ""