@rakeshr Thanks for replying. I already know what you mentioned. That is only 1 of the 2 needed inputs. Hence that doesn't solve my requirement.
I want to compute the volume weighted average price for an interval. For that I would need either 1) p…
HAPPENED AGAIN WITH ADANIENT
Order #: 180711000141078
See stoploss level is not reached:
The above image of stoploss having gotten triggered is the second image. It showed as triggered a few minutes back too.
@sujith No. It does not depend on the number of trades. It's always only OPEN AND COMPLETE in Case 2.
You were wrong in Case 1 also.
In case 1, the only updates are OPEN and CANCELLED.
@sujith
Your answer on June 20 was incorrect. Please take DUE CARE with your replies.
I am referring to your below answer.
For case 1 you will receive 3 order updates with status OPEN, UPDATE and CANCELLED.
For case 2 you will receive 3 order upd…
@Zerodha team:
Today, when I placed an order at around 3:21 pm, there was a momentary error. I guess it was because the order queue was choking from automated exits of intra-day orders being done by Zerodha's systems. Interestingly, my order which …
By the way, if you can informally share a quick list of order statuses sent via postback, I will be able to continue my development. It's a humble request Thanks.
On [email protected] please.
@sujith Thanks a lot!
.... and so there is an OPEN status too. I wish I knew about it earlier. I will have to rework. Sigh!
Documentation on postbacks (https://kite.trade/docs/connect/v3/postbacks/) -
Only mentions these - COMPLETE, CANCEL, REJ…
@sujith Thanks.
Please answer the following:
Say I place an order for 100 shares with validity=IOC. What will be the postback status (CANCEL / UPDATE / COMPLETE / REJECTED) in the following 3 cases?
Case 1: 40 got filled, remaining 60 got cancell…
@codezed Thanks. Yes, I am looking for websocket response. Polling order book is inefficient, on 2 counts - 1) program's response to order execution gets delayed until the next poll iteration, 2) polling increases load on Zerodha's servers because …
Sorry, I've to ask for more details as I can't test it myself.
Say I place an order for 100 shares with validity=IOC. What will be the postback status (CANCEL / UPDATE / COMPLETE / REJECTED) in the following 3 cases?
Case 1: 40 got filled, remainin…
@tonystark Market order can only be used with highly liquid securities. For other securities, I would use market order only to stop loss. For position initiation, I strongly prefer limit order (with reasonable impact cost).
With limit orders, wait…
@ tonystark Place yourself in the shoes of a client-side developer who wants to use WebSocket order postback. Say you place a Limit order on SBIN to buy 1000 shares. Since postbacks are asynchronous, you program can't wait for the order execution. Y…
@ sujith,
Could you please add more details on IOC orders in the documentation, maybe with sample code? This will be useful to Zerodha as much as the traders because IOC orders could help people transition from polling order book to asynchronous ord…
@anneraghu , @sujith
Regarding "16388 : Unmatched orders cancelled by the system" -
Understand that this is for IOC orders. Is it an exception thrown by kite.place_order() or is it received by the on_order_update() callback? Or somewhere else?
I…
@vivek : Since ticks received on WebSocket will usually be processed to generate trade triggers, the WebSocket and the strategy implementation code (which will make API requests) will both be best hosted in AWS Mumbai, right?
@sujith : Was this looked into yet?
To summarize the issue, a SL order placed without the "price" input degenerates into a SL-M order. Is this expected behavior?
Thanks.
Since your sandbox ETA is a moving target, could you provide free API access once a month, only on the mock trading day, only for registered zerodha clients?
This is wrong:
kws = KiteTicker(
api_key,
public_token,
user_id,
)
It should be like this:
kws = KiteTicker(api_key="api_key", access_token="access_token")
Hi Detrader,
I am wondering if you need to run kws.connect twice:
kws.connect(threaded=True)
kws.connect(disable_ssl_verification=False)
Try running kws.connect only once. Set both threaded=True and disable_ssl_verification=False in one call…
