The historical data API is provided for backtesting purposes only. We recommend generating candles at your end using the live market data provided via Websockets API for live market strategies.
Kite Ticker data is not a public data feed, it is data provided by the exchange for members with certain restrictions. I am afraid we can't provide this feature.
You can talk to compliance for more information about it by writing to kiteconnect(at)z…
The instrument token is unique only for the current day. It can be reused by the exchange once an instrument expires. It is recommended to store a combination of exchange and tradingsymbol as the key.
@vishnux,
Kite Connect doesn't offer backoffice or reporting features. It currently offers only trading platform APIs only.
You will have to store values everyday and do it at your end.
Thank you for pointing this out. This got missed in the refactoring. It is supposed to be tradable for all instruments except for indices. We will make the changes in the next release.
Since candles are formed at our end like how it is mentioned in the thread for all instruments that are traded for the day, it is not guaranteed that at the end of the minute the candle is formed.
@vivekmanot,
The historical data is provided for backtesting purposes only. You need to fetch the whole dump in the loop at your end and use that as the source.
For live strategies, we recommend you to make candles at your end using the live market …
@sachinstlko09,
The formatted tradingsymbol is just for readability purposes only. It has nothing to do with search.
A plain text search on the instruments dump should do the job. If you want to further optimize the search you may breakdown the lis…
@sodha_rakesh,
You will see the year in the formatted tradingsymbol only when the year is not the current year.
This shouldn't affect the Kite Connect users at all, since we don't use this anywhere on Kite Connect.
@sourirajan,
Kite trade has to still place order on OMS for exiting a position. Error management becomes difficult and Kite Connect has always been simple and modular APIs, we want to keep it absolutely an execution platform.
Kite web just abstract…
I am afraid we can't make any changes. This flow is similar to all OAuth flows. It's not misleading at all and the user has to see and acknowledge that they're logging into a certain service using Kite.
You can check out the API documentation to know the response format for placing an order.
You can use order history or orderbook to know the latest status of the order.
The order history is a list of various states of order in the system. The late…
It is a mechanism Kite Ticker uses to see if the client is connected or not, you can just add a length check at your end. If ticks length is 0 then you can ignore it.
You can run pykiteconnect with debug logs on and check what exactly you are sending.
If you don't understand then please post the complete stack trace here by removing the app tokens, we will check and get back to you.
You can make any number of requests. You need to make sure you don't hit API rate limits i.e requests/second limit. You can know more here.
Historical data is intraday or day candle data. You can know about the response format here. You can check o…
You need to use Websockets for fetching live market data and not poll Quote APIs.
You need to call order history only when there is a websocket order update.
This the response i see
{"status": "success", "data": { "candles":[["2020-12-16T00:00:00+0530",1952.25,1962.25,1935.45,1951,4152400,22514800]]}}
Can you run with debug logs and paste the complete stack trace here?
Make sure to remove session and app…
Can you let us know about the setup and the pykiteconnect version?
Also please include the code and complete stack trace, we will check and get back to you.
@shan_muga_09,
No, you will have to subscribe to get the same day's historical data as well.
But for live market strategies, we recommend you to generate candles at your end using the Websocket data.
It depends on your use case, if it is a contained app which just does some calculation and place orders then a simple core java app would do. But it is better to go with whatever you are comfortable with.
You can check out this discussion for storin…
If you have a cash position that needs to be carry-forwarded then it goes to your holdings.
On the same day, you can see it on the positions tab but the next day, it will be under holdings.
A non-POA client has to authorize every Demat debit at the…
@jinalpatelcsoft,
The postback is sent by the OMS team, we will ask them to look into this. In the meanwhile, we suggest you use postback as the trigger to fetch orderbook and check if the value is updated.
I am afraid we can't do that. We are just technical guys here, we don't make business decisions. You can ask business-related queries by writing to kiteconnect(at)zerodha.com
@meeashok,
In this sheet https://docs.google.com/spreadsheets/d/1ZTyh6GiHTwA1d-ApYdn5iCmRiBLZoAtwigS7VyLUk_Y/edit#gid=0
on the right-side column, it is updated under the temporary ban list.
if there is no automatic process or there is nothing from api, it will be difficult to approve each and every transaction for selling. because algo trading (python) can buy daily 100 transactions, so as you know it will be difficult to muaually appr…
As long as you have a valid access token, you can place orders from multiple systems. I am hoping this is for running different strategies on different machines.
You may need to watch for this.
Once you run Kite Ticker, it keeps receiving ticks. You shouldn't block the thread at all. You need to offload your calculations to a secondary thread.
@rjbanna,
I am afraid, third-party websites can't show our live market data on their website. You can write to compliance with the product description on kiteconnect(at)zerodha.com for more information.
@dhirs,
If the historical data Kite Connect offers don't serve your purpose then you can build candles at your end using the live market data provided via Websocket API. We usually recommend generating candles at your end for live market strategies.…
