Delete Trades List
MngDeleteTradesList¶
Description: Allows a manager to submit delete requests for multiple trades at once by specifying a list of order IDs.
Warning
this method work only for closed trades
Access Control¶
Requires del_trades for manager/dealer sessions. The target account must also match the manager groups and brand scope loaded from the cached manager record. Token payload is used only for manager id and session type.
Request Parameters¶
| Name | Type | Required | Description |
|---|---|---|---|
| orders | array | Yes | List of trade order IDs to delete (integers) |
| __access | object | Yes | Access object containing session type information |
Request Example¶
{
"orders": [1001234, 1001235, 1001236],
"__access": {
"type": 1
}
}
Response Parameters¶
| Name | Type | Description |
|---|---|---|
| rows | array | Successful delete acknowledgments |
| matched | integer | Total number of requested orders |
| deleted | integer | Number of orders accepted for delete processing |
| failed | integer | Number of orders that failed validation or enqueue |
| failures | array | Optional per-order error details for failed delete requests |
Response Example¶
{
"rows": [
{
"accepted": true,
"order": 1001234,
"state": 8
},
{
"accepted": true,
"order": 1001235,
"state": 8
}
],
"matched": 3,
"deleted": 2,
"failed": 1,
"failures": [
{
"order": 1001236,
"error": "RET_NOT_FOUND",
"message": "Trade not found"
}
]
}
Notes¶
- A successful response is an acknowledgment that the delete request was accepted, not confirmation that final processing has completed.
orderis the correlation identifier for subsequent trade lifecycle events.- If no orders are accepted, the method returns
409. - If some orders are accepted and some fail, the method returns
207.