Update notification
MngUpdateNotify¶
Description: Updates an existing notification record from a manager-side TCP session.
Unlike the client REST method, manager update is wide and can modify notification payload and metadata.
Request Parameters¶
| Name | Type | Required | Description |
|---|---|---|---|
| id | int | Yes | Notification ID to update |
| user_id | int | Yes | User ID associated with the notification |
| token | string | Yes | Unique token identifier for the notification |
| message | string | No | Notification message text |
| description | string | No | Extended plain-text description |
| data | object | No | Structured data payload |
| type | int | No | Notification type |
| level | int | No | Notification level |
| status | int | No | Notification status |
| access | int | No | Notification access |
| open_time | int64 | No | Optional open time (Unix timestamp) |
| create_time | int64 | No | Optional creation time (Unix timestamp) |
| exp_time | int64 | No | Optional expiration UNIX timestamp. 0 clears expiry |
Request Example¶
{
"id": 101,
"user_id": 123456,
"token": "TRADE_REJECTED",
"message": "Updated: Content changed.",
"description": "Updated manually",
"data": { "reason": "manual-review" },
"type": 1,
"level": 2,
"status": 0,
"access": 1,
"exp_time": 0
}
Response Parameters¶
| Name | Type | Description |
|---|---|---|
| data | string | Returns "OK" if successful |
Response Example¶
{}