Kite Connect API is the only documented and authorized way for programmatic access. Scripting and scraping the website is against our terms of service. Technically it is also prone to breaking as the frontend changes without notice.
The instruments master keeps changing everyday, on NSE few instruments are moved to T2T segments and back to EQ. It happens on BSE also sometimes. We don't have a list like that.
PS: In the world of trading change is the only constant
@tahseen,
Though tradingsymbol is same for most of the cases, there are edge cases wherein trading symbol is different for same instrument on different exchanges. The solution is to introduce a field which is ISIN based on which it will be easier to…
v4 is the version of the gokiteconnect and not the Kite Connect API.
You can find the v4 documentation of gokiteconnect here.
The new API endpoints are just added as section in the API documentation.
@BibinVargheset,
You need to put all orders in a list and place it in loop.
OMS doesn't have bulk order place API and hence you will have to place each order in the loop at your end.
@BibinVargheset,
You can place an order with opposite transaction type and same quantity, exchange and product for a regular order and call exit order for cover order.
We never recommend using Kite Connect for HFT or time based strategies. For how many instruments are you fetching the data and how often do you fetch the data? Is this consistent or intermittent?
Unfortunately with the current setup, we can't make changes to the sheets or the format of the sheets.
We will find a better solution in the future.
MIS product will by default have the leverage if provided for that by us or else you will need ful…
The margins data API will be deprecated. You can use this API instead of doing calculations at your end.
This API will consider your pending orders and positions as well for calculating margins required.
@satish_p,
You can know more about it here.
You can setup a server at the exchange premises to get tick by tick data. The cost is upwards 18 lakhs per annum. You can email kiteconnect(at)zerodha.com someone from our team will help you out with sett…
@KamalChhirang,
We just make a call to OMS to place an order, if we get timeout instead of order_id then we won't know if order is placed or not.
We also get to know after orderbook is updated.
@shankars,
We don't see any issue at our end. All the candles seem fine. We use the tick data to form candles and if there is Rs 1 as low then it should reflect in any of the candles but we don't see any candle like that.
You need to use order_update as the event for fetching orderbook and checking the latest status and other fields.
They are asynchronous messages pushed by OMS and we just relay and they are out of orders in some cases.
@AD6499,
You need to fetch candles and dump it at your end and use that as source for backtesting.
For live market strategies, we suggest you to use generate candles at your end using the live market data provided on the Websockets API. You can get …
Only order updates are pushed via Websockets API. You will need to use the REST like http API to fetch orderbook and positions. You can refer to the documentation here.
There can be hundreds of ticks in a second at the exchange any trading platform over the internet can capture only 1- 2 ticks over the internet. So the candle data you see is only a trend and not the accurate data.
For accurate data, you will need t…
Can you check what is the status code?
Is it 429?
Also, we need more info on that specific amo order.
Can you paste here the output of getOrderHistory(that amo order_id)?
We have plans of providing this but it is getting postponed since it is a breaking change and other high priority tasks came in between. I will ask the team to take a look at this.
You can place order after the first tick. You will have to open the websocket connection and wait for the tick of that instrument and then place order from there.
In few less liquid instruments the first tick can be at 9:17 or 9:19 AM
PS: Websocket…
@lotusdew,
Please write to kiteconnect(at)zerodha.com with product details and more details about your company and the process you follow. Someone from the compliance team will get back to you and help you out with how to get started.
Kite Connect doesn't have support. We just help out the community developers here. We are all developers like you. There are no support executives.
You can read the previous reply properly and you will get your answer.
This happens when OMS doesn't respond with order id and Kite Trade times out. We have informed the concerned teams to look into this.
PS: If you are doing a retry, you need to fetch orderbook and check before you do a retry of placing the order.
You can go through the documentation.
We don't manufacture data, we just relay whatever exchange publishes.
You can make candles at your end using the live market data provided on Websockets API. You can get started here.
We haven't done any changes to ratelimits. You can log all the requests at your end and check.
If you enable debug log while doing init, you can see all requests and responses.
@hkr,
The historical data API is provided for backtesting purposes only. For live market strategies, you can generate candles at your end using the Websocket API data.
You can get started from here.
It is difficult to say where is the error coming from. Since there are a lot of variables involved. Your script must be able to wait for a few milliseconds or seconds and then retry if it is a GET call. If it is a POST/PUT/DELETE call then you need …
@sagarverma1919,
You can speak to the compliance team before starting the project. You can write to them on kiteconnnect(at)zerodha.com with product details and someone from the team will get back to you.
@sagarverma1919,
Are you converting to json?
This is an exponential representation, you can convert it to decimal or format it. Maybe in coming releases we will change it to long.
Yes, if it is EQ series then Kite Connect doesn't add -EQ, but for other T2T segments, we add series.
Please note that NSE and BSE have different types of tradingsymbol naming for T2T segments. You can read more about it here.
