Namaskara,
GetOrderDetails returns the following response body:
{
“status”: “success”,
“data”: {
“exchange”: “NSE”,
“product”: “D”,
“price”: 571.0,
“quantity”: 1,
“status”: “complete”,
“tag”: null,
“instrument_token”: “NSE_EQ|INE062A01020”,
“placed_by”: “******”,
“trading_symbol”: “SBIN-EQ”,
“tradingsymbol”: “SBIN-EQ”,
“order_type”: “LIMIT”,
“validity”: “DAY”,
“trigger_price”: 0.0,
“disclosed_quantity”: 0,
“transaction_type”: “BUY”,
“average_price”: 570.95,
“filled_quantity”: 1,
“pending_quantity”: 0,
“status_message”: null,
“status_message_raw”: null,
“exchange_order_id”: “1300000025660919”,
“parent_order_id”: null,
“order_id”: “231019025562880”,
“variety”: “SIMPLE”,
“order_timestamp”: “2023-10-19 13:25:13”,
“exchange_timestamp”: “2023-10-19 13:25:13”,
“is_amo”: false,
“order_request_id”: “1”,
“order_ref_id”: “GTT-C23191000044253”
}
}
My queries:
- “price”: 571.0 → Should be “filled_price” isnt it?
- “status_message”: null,
“status_message_raw”: null → Both Status_Message and Status_message_raw are of type json::string… Therefore the correct value for the these keys when there is “no Status” is “” (null string) and not just null. If its “” then its easier to process the information as I need not compare the value against a string “null” to determine the absence of a message. - “variety”: “SIMPLE” → Please list the complete set of values for this parameter, here.
- “order_timestamp”: “2023-10-19 13:25:13” → This was the exact request I had for the expiry date in complete.json file, in one of my earlier posts… at that time I pointed out that UNIX EPOCH TIME was hard to comprehend.. rather we should have Date in DD/MMM/YYYY format. isnt it funny… what I wanted is implemented here…but not in complete json file!!
- “parent_order_id”: null : Parent Order ID is integer, hence the root of that is always 0 and not null.
Kindly harmonize the json data type and the NULL of that value in the same data type.
Regards
Rathnadhar K V