MODIFY ORDER
This API enables modification of existing orders for authorized end users through a middleware-based integration.
Only eligible pending orders can be modified.
🔗 Path Parameters
| Parameter | Type | Required | Description | Example |
|---|
| exchange | string | Yes | Exchange segment in which the order is placed | "MCX_FO" |
| order_id | string | Yes | Order ID of the order to be modified | "NXVZO00086K1" |
🔍 Query Parameters
| Parameter | Type | Required | Description | Example |
|---|
| userId | string | Yes | User ID (UCC) | "{{user_id}}" |
| Header | Type | Description | Example |
|---|
| Content-Type | string | Request payload format | application/json |
| Authorization | string | Access token for authenticated requests | {{access_token}} |
| x-api-key | string | API key used to authorize request | {{x-api-key}} |
📑 Request Body Parameters
| Field | Type | Required | Description | Example |
|---|
| order_type | string | Yes | Type of order | "LIMIT" |
| quantity | integer | Yes | Modified order quantity | 100 |
| traded_quantity | integer | Yes | Cumulative traded quantity of the order. Available in Order Book response | 25 |
| price | number | No | Modified order price in rupees | 1500.50 |
| trigger_price | number | No | Trigger price for Stop Loss orders | 1495.00 |
| disclosed_quantity | integer | No | Quantity to be disclosed to the market | 50 |
| validity | string | No | Order validity | "DAY" |
| validity_days | integer | No | Number of days for GTD validity | 30 |
🟢 Success Response - 200 OK
Content-Type: application/json
| Field | Type | Description | Example |
|---|
| status | string | Status of API call | "success" |
| code | string | Response code | "s-101" |
| message | string | Order modification success message | "Order modified successfully" |
| data | object | Order response details | Refer Data Object Fields |
📦 Data Object Fields
| Field | Type | Description | Example |
|---|
| orderId | string | System-generated order identification number | "NXVZO00086K1" |