@rakeshr the api call provides the necessary info for about 500 scrips in one go whereas for the python call you'll have to build each and every order_param_multi .
Can we get an array or dataframe through python API exactly same as what's being …
@Vivek Thanks for the reply.
While I appreciate all your help and try to be a civil user by sticking under the prescribed rate limit, it infuriates me to spend countless hours to debug the application and be in the receiving end to know that the ch…
@Vivek - thanks for looking!
200 request per min roughly translates to 3request/sec. Whereas the limit mentioned earlier was
Quote API - 1r/s
Order place API - 5r/s
Historical API - 3r/s
All other endpoints - 10r/s
https://kite.trade/forum/discus…
@sujith - thanks!
Single request - updating SL for open orders. 2 parallel thread to update a list of 'n' orders. The threads waits till there is an API response (so I don't consciously try to push x number of orders per seconds). Usually this api …
^ Essentially same question - still unanswered. https://kite.trade/forum/discussion/5219/method-to-calculate-leverage-in-equity-screenshot-provided#latest
Thanks @sujith and makes sense.
One question is still unclear to me:
How do I deduce from this API that the CO leverage has been changed from 20.8x to 16.7x for Nifty50 stocks (cash)? Earlier I used hardcoded 20.8 value to deduce margin/quantity t…
Hi Rakesh ,
why is it different from kite.margins(segment="equity") -- that shows margin for user's details and not scrip level information.
Also you explained - ""co_lower": 4% is the margin requirement of contract value for CO." Does this transl…
@rakeshr
Any particular reason for this?
From outsider's perspective it would make more sense for the kite userbase that zerodha maintains the data than individuals do that for the sake of consistency, usability and maintainability.
@sujith Thanks. Here's what my understanding is - let me know.
Midnight - 4:00 AM - BOD process - kite might be unavailable
4:00-7:00AM - kite api should be available (mostly) . Previous days access token should work
~7:00 AM - Previous day's acce…
@sujith - sorry what is BOD? Also - what does the login process has to do with OMS?
I hope I am not coming across as rude, just curious to understand the architecture.
@Shaha
Rightly said and exactly that's why I am not interested or asked for your trading strategy - rather I am interested in discussing the technical infrastructure that you use for your "algo" trading (if you use kite api at all). Do you use any…
@Shaha
Congratulations! Can you share your technical details as well (which api you use, trading timeframe, how much of it is automated, capital deployed etc.)
This is really inspirational.
@Nikhil.A
Originally, the idea with the APIs was to find new ways to get more retail participants to enter the markets. In order to encourage people with ideas to do this, APIs for startups are free.
Is it not true anymore? Any plan to shut down th…
@sujith
Exactly my point. This is why increasing the order close api threshold limit from 3/s to 5-6/s will help developers close out the positions in much efficient manner before hitting 3:20. Do you think this is possible?
The other option woul…
@nithin, @sujith
That's a good initiative. 20 admin fee per day and not per open order I suppose? Otherwise the admin fees (if incurred) will be skyrocketed as the api orders tend to be large in number in order to reduce impact cost.
Keeping this…
@Kailash @vivek
With the speed up in latency and more volume handle capability, would you consider increasing the api call limitation (3/sec) to something more flexible like 5/sec?
Also - would it be possible for you to add a features in api call…
@Kailash This means there isn't any IP Address specific restriction. Am I correct in my understanding?
For a trading server with multiple user (different API Key) this will be very helpful.
Also - do you think the rate can be changed to bit more le…
I receive the same error when using 4 threads which roughly translates to 4 requests/second. I have seen somehow 3 req/second works.
Note: the requests are SL modification for BO/CO and not any websocket call.
@vivek
5. My suggestion was to have a generic way to get several order details in a single call rather than gathering the whole kite.orders() call. Do you think this can be accommodated anytime in the future?
6. Similar to (5) -- but an ability to…
Fantastic suggestions. May I add:
5. the ability to pass an array to kite.orders() call.Currently kite.orders() fails frequently with OMS Timeout in case number of orders (completed + pending) are more than 70-80. Even though the actual orders are …
@soumyadeep @Kailash @vivek
Yes - this is a problem I faced several times. Usually after for 40-50+ orders, I keep on getting the Gateway Timeout error. I think it is something to do with a timeout parameter setting somewhere. One more observation…
Getting Gateway timeout error today. Is this due to 7 second timeout configuration I saw somewhere in python client? Can this be increased? I am making a call for kite.orders() for about 200 orders.
@Zerodha team/ @Kailash
Even after 30 mins of the post above, I am getting timeout error whenever I am calling kite.orders()
A strange behavior that today I have placed a lot of small orders a total of 69 and do you think it is failing just becaus…
@Kailash
If this is arbitrary timing, do you think, it will be possible to move the timing to say something like 6:30 AM or 7AM till a long standing token is implemented?
@Kailash
Thanks! Is there any rationale behind the timing for 8:15 AM? Curious if this can be scheduled earlier as well - say 7:15 AM? Also -- would you mind sharing the the high level solution of how you are planning to achieve a long standing ac…
There can be cases when BO is executed but the TSL doesn't move. The TSL will be active only when it crosses a threshold.
Example: you place a BOfor stock at 100 and expects it to move up. The CMP is 99.5. You want the SL value to be 98 and trailin…
@RH1558
Trailing stop loss moves in only one direction. If your stock moves in a profitable direction the trailing SL moves in the direction of stock to make sure it adjusts to the new price. Any reverse direction taken by the stock will *not…
@vivek
Thanks! Could you please tell me the time on when exactly the validation window starts? Midnight, 7am, 8 am or market start?
I mean what is the maximum range of time window, an access token can remain valid?
Exactly!
When this is charged and the platform is not in beta status. It's been almost 1 hour and the issue is still ongoing. Please note that this is not a social media api and rather a trading api where huge amount of money is involved.
I stron…
@vivek ,
"OMS connection error" and "Gateway timed out" -- are they both related to OMS vendor? While the first error prevents any order through the second error actually lets the order put into the system which is extremely risky behavior.
@Nikhil.A,
Does this mean - we need to do a separate login every day via https://kite.zerodha.com in addition to loggin in through the application via apikey?
@Kailash,
Other than OMS Timed out I have encountered several other errors today. Surprisingly - the same order executed couple of seconds before through the same code.
Please see that the same order for SBI was successfull at 9:49:58 but failed…
@Kailash - I will add exact timestamp for next executions. However, these errors happened somewhere between 9:50-9:51 and few happened around 10:04-10:05 on 29th June.
@Kailash
Nevermind - the last bit of code works. The order_id value wasn't correct. Passing variety='co' solved the issue.
Suggestion: can the python document be updated to explain the mandatory parameters and their values? Seeing the code it see…
@Kailash ideally, when modifying a CO, only order_id and trigger_price should be passed. Isn't it?
I tried the following call:
kite.order_modify(order_id=row['order_id']),trigger_price=row['sl_price_new'], variety='co' )
Still failing with error:…
@Kailash -- after adding the variety='co' parameter, I am getting the error as:
'Not a second Legged Cover Order.'
my order_modify call now looks like:
kite.order_modify(order_id=row['order_id']),tradingsymbol=row['tradingsymbol'],exchange=row['e…
Hi Kailash,
Any help on this please? Even though I pass on all the required parameters - the exception message is "'Cannot Modify a Cover Order.'"
The order_ids correspond to 21-June trade and were tried around 10-11 am.
