Skip to main content

Modify GTT Order

This API allows you to modify an existing GTT order that is pending in the order book.

🛣️ Endpoint

PUT {{hosturl}}/transactional/v1/orders/regular/:market/:orderID

🛣️ Path Parameters

FieldsTypeRequiredDescriptionExample/Enum
marketstringYesExchange segmentsNSE_FO
orderIDstringYesOrder ID to be modified (URL encoded format)NYMKL00016;<

🔑 Header Parameters

FieldsTypeRequiredDescriptionExample/Enum
AuthorizationstringYesBearer token for authenticationaccess_token
x-api-keystringYesAPI key provided by brokerx-api-key
Content-TypestringYesMust be application/jsonapplication/json

📦 Request Body Schema

FieldsTypeRequiredDescriptionExample/Enum
scrip_infoobjectYesInstrument exchange infoSee below table
order_typestringYesOrder TypesRL / SL / RL-MKT
quantityintegerYesUpdated quantity for the order75
pricenumberYesUpdated limit price25500
trigger_pricenumberYesUpdated trigger price23000
disclosed_quantityintegerNoQuantity to disclose publicly0
validitystringYesOrder validity type. Must be GTTGTT
validity_daysintegerNoNumber of days the order remains valid0
traded_quantityintegerYesAlready traded quantity (fetch from order book)0

📘 Scrip Info Object Fields

FieldsTypeRequiredDescriptionExample/Enum
exchangestringYesExchange segmentsNSE_FO

📋 Sample Request Body

{
"scrip_info": {
"exchange": "NSE_FO"
},
"order_type": "RL",
"quantity": 75,
"price": 25500,
"trigger_price": 23000,
"disclosed_quantity": 0,
"validity": "GTT",
"validity_days": 0,
"traded_quantity": 0
}

🟢 Success Response – 200 OK

FieldsTypeDescriptionExample/Enum
statusstringAPI call statussuccess
codestringResponse codes-101
messagestringSuccess messageOrder Modification Sent to OMS
dataobjectContains the modified order IDSee below table

📘 Data Object Fields

FieldsTypeDescriptionExample/Enum
orderIdstringSystem-generated modified Order ID"NYMKL00016;<"

📋 Sample Response

{
"status": "success",
"code": "s-101",
"message": "Order Modification Sent to OMS",
"data": {
"orderId": "NYMKL00016;<"
}
}