Add notification
MngAddNotify
Description: Creates a notification from a manager-side TCP session.
Request Parameters¶
| Name | Type | Required | Description |
|---|---|---|---|
| user_id | int | Yes | Target user id. Use account login for client notify or manager id for direct manager notify |
| token | string | Yes | Unique token identifier for the notification |
| message | string | Yes | Notification message text |
| description | string | No | Optional plain-text description |
| data | object | No | Optional structured payload |
| type | int | Yes | Notification type |
| level | int | Yes | Notification level |
| status | int | Yes | Notification status |
| access | int | No | Access scope |
| exp_time | int64 | No | Expiration UNIX timestamp. 0 means no automatic deletion |
Manager-specific behavior:
- when
access = 0(NOTIFY_LEVEL_MANAGER), a single direct manager notification is created foruser_id - when
access = 2(NOTIFY_LEVEL_ALL_MANGERS), the server creates a separate notification record for every enabled manager user_id = 0is deprecated and should not be used for new requests
Request Example¶
{
"user_id": 123456,
"token": "TRADE_REJECTED",
"message": "New trade alert: Your position on EURUSD has been closed.",
"description": "Trade was closed by Stop Loss.",
"data": {
"order": 58123
},
"type": 2,
"level": 0,
"status": 1,
"access": 1,
"exp_time": 0
}
Response Parameters¶
| Name | Type | Description |
|---|---|---|
| data | string | Returns "OK" if successful |
Response Example¶
{}