The 2nd leg has been executed approx 20:03 IST, however the execution time returned by Kite is same as that of fist leg. Is this the expected behavior? If yes then how can I get exact exchange execution time? I guess this is incorrect and it should have correct execution time.
Note: Zerodha web/android app are also showing same behavior i.e. incorrect (or same as 1st leg) time for 2nd leg.
@sujith Sorry, didn't get you. I am using "exchangeTimestamp" field from Trade class. It is giving me same timestamp for both legs. Could you please check whether it is a defect or expected functionality?
execution_time (as per Kite) : 2018-01-18 19:24:55 -- This is what I have received from Kite API in Trade object (exchangeTimestamp).
Actual execution_time (approx): 2018-01-18 20:03:07 PM -- This is the time when it got actually filled on exchange.
Kite API should have forwarded the trade exchangeTimestamp ( for Trade ID: 210067144) as 20:03, however it was 19:24 which looks incorrect to me. Please share your findings on the same.
@ruchanavjyot1907, The exchange timestamp is actually the exchange entry time. Once a bracket order sits as open and when market conditions are met, there will be two orders placed and both will have same exchange timestamp as the time difference in placing an order at exchange will be in few milliseconds. Let us say after sometime target gets completed as market conditions are met. A cancel request is placed at the exchange and hence exchange entry time gets updated.
@sujith If I understood your last statement correctly, then time should have been changed to latest when second order got filled at exchange. However, I am getting previous time only even after it got filled after 30-35 mins.
@sujith Please go through complete discussion. I have already informed that I am expecting correct execution/fill time in "exchangeTimestamp" field from Trade class while receiving trade information from Kite API.
Can you let us know, what is this value execution_time and Actual execution_time?
execution_time (as per Kite) : 2018-01-18 19:24:55 -- This is what I have received from Kite API in Trade object (exchangeTimestamp).
Actual execution_time (approx): 2018-01-18 20:03:07 PM -- This is the time when it got actually filled on exchange.
Kite API should have forwarded the trade exchangeTimestamp ( for Trade ID: 210067144) as 20:03, however it was 19:24 which looks incorrect to me. Please share your findings on the same.
The exchange timestamp is actually the exchange entry time.
Once a bracket order sits as open and when market conditions are met, there will be two orders placed and both will have same exchange timestamp as the time difference in placing an order at exchange will be in few milliseconds.
Let us say after sometime target gets completed as market conditions are met. A cancel request is placed at the exchange and hence exchange entry time gets updated.
You mean order_time?
Please go through complete discussion. I have already informed that I am expecting correct execution/fill time in "exchangeTimestamp" field from Trade class while receiving trade information from Kite API.
You are referring to exchange_timestamp of trades response, right?
I will check and let you know tomorrow.