Please go through the code and understand what you are trying to implement. You need to look into the ticker usage code.
These examples are meant to demonstrate usage, not just copy-paste.
This is just a warning, it won't cause the script to stop.
Maybe you don't have kiteconnect in the default path you are using.
You need to check the python path and the installed kiteconnect path.
If you have subscribed today then you need to re-create the access token for using the historical data.
You need to print the exception message to know the exact issue or run javakiteconnect with debug logs true while creating the object.
You may use the combination of tradingsymbol and exchange as the key.
The exchange will not change but instrument token may change but changing instrument token for EQ is rare but when it is moved to the T2T segment it does change.
@ak1194,
This could be because the request could have timed out by the time data is fetched. You need to catch the exception and retry after a small delay.
This is a third-party library and doesn't have any restrictions on using the code, based on the licensing for the repo. You can fork it and add Websockets feature to the same. You can go through documentation here.
We would be happy to assist you i…
We will look into the possibilities.
It might take a while since this is a huge requirement for our OMS vendor which may never happen from their end, but we will do it on our system and it involves a lot of backend work as multiple systems need to s…
Kite charts use the same historical data.
If you are dealing with live market data then I would suggest building candles at your end using the live market data provided using Websockets.
You can refer to this thread to know about ATP and VWAP.
If we use enums then users won't be able to pass new values that are newly added. That's why we use string constants.
This will make sure the existing library will work for new types also and we can add these new constants any time.
@Anuj, @Upanshu,
We have populated all the data we have. If intra-day candles don't exist then we may have to get it from somewhere else and populate it. We may do it in the future but we can't do it right now.
This is because the stock is moved from EQ series to the T2T segment which means, only delivery trades are allowed for the non-EQ categories.
When exchanges suspect speculation or some irregularities in stock then to curb the liquidity it is moved t…
We don't recommend pull historical data for live strategies or scanners. You need to generate candles at your end using the live market data provided via Websockets.
You can refer to this thread.
You can refer to these threads.
https://kite.trade/forum/discussion/6093/connection-error-1006-connection-was-closed-uncleanly-none#latest
https://kite.trade/forum/discussion/7399/kiteconnect-ticker-connection-error-1006-connection-was-closed-uncle…
Hi @sivannarayanagunji ,
Input Exception or a parent exception type Kite Exception are custom exceptions that are structured like this.
You may also check out similar exceptions thrown by Kite Connect in that directory.
OMS runs the BOD process everyday post 12:30 AM to early morning 05:30 AM. Earlier, we used to send orders to OMS but now we are rejecting such orders at our end.
If the rejection happens at our end then you won't see the entry in the orderbook.
You will have to use Webview for login and pick up the request token from the redirect URL.
At the server, you need to exchange request token to access token.
One shouldn't poll positions API to get the latest P&L, that is a bad practice. You need to use either Quote API or Websockets to fetch live market data and calculate P&L at your end.
This is what I am getting in the instruments master dump.
10006530,39088,NIFTY20DEC10700PE,"NIFTY",0,2020-12-31,10700,0.05,75,PE,NFO-OPT,NFO
We don't have timezone type and timezone in the instruments CSV dump.
