A Kite Connect app by default is provided for personal use only. You will have to use it with the client id which was provided while creating the Kite Connect app.
Margin calculation API has been provided for this purpose for from a very long time (more than a year or two). We had recommended to use new endpoints.
These endpoints are kept for legacy reasons and will be deprecated soon.
A Kite Connect app is provided for personal purpose only. Hence you can only use it with the client id with which it was created. If you have only one account with Zerodha then go to app details screen and check if you entered the correct client id.…
You can save all the live market data from Websocket API and use that for your analysis or convert it to candle data use that for analysis.
For older data, you need to pull historical candle data and dump it in your database and use that as source.
Kite Connect only offers trading platform capabilities. Every day after BOD process is run, all old data is cleared. You will have to store orderbook everyday at your end to do this.
You can reach out to the business team with the screenshot and developers console id. They will check and get back to you. You can write to them on kitconnect(at)zerodha.com
One way is to fetch orderbook after one or two seconds and check if the requested parameter is updated or not, if not updated then the status_message field will have the reason.
Another way is to fetch order history and check.
It is 200 requests per minute for order place, modify and delete order.
I don't think we will support bulk order cancel API.
OMS doesn't support bulk cancel. Even if we support, we will have write a loop and place requests one after the other.
The historical data API is provided only for backtesting purposes. We don't recommend polling that for live market strategies. We suggest generating candles at your end using the live market data on Weboscket API.
You can get started here.
You might be getting blocked by our CDN, it could be happening because it is considering your requests as DDOS attack. You may use Websocket API to fetch live market data.
Intraday candles are not provided for expired instruments.
For continuous data, please note that we only provide day candle data for futures instruments.
Placing GTT with an order is a feature exclusive to Kite web and app, you can use order updates via Websockets and place OCO GTT once an order gets filled or completed.
Kite Connect only has trading capabilities, it doesn't have any backoffice features. It is not possible to automate Kill switch using Kite Connect APIs.
The same API is being used by all our platforms. It is very unlikely that this is happening. Can you enable debug logs and share the complete request and response json.
PS: Make sure to remove app and client specific tokens.
We don't see any issue at our end.
The same Websocket API is used by all our apps including client facing ones and internal ones. It is also used by more than 10 thousand live Kite Connect apps.
You need to make sure you are not blocking the threa…
We have asked the team to take a look at this. But it might take more time to fix. There are tens of thousands of AMOs fired at that time and traffic is very high at the market open. We suggest placing order after a few seconds.
The instruments master file doesn't require authorization header but a Quote API call does require.
You may enable debug logs for pykiteconnect and check the request and response json. As error message suggests, you might be sending wrong api_key or…
You will get postback for every partial fill as well, but we suggest you to use postback as an event and fetch orderbook and check filled quantity for latest status on the orderbook.
There are few edge cases wherein OMS sends multiple postbacks, on…
For order placement, the variety co must be used and product will be MIS. The product CO is only present in the orderbook. Since it is not prominently used, you can ignore CO product as it may lead to more confusionf for new users.
For all intraday…
Instrument token is derived from the exchange token and the segment. But you never know since exchange only keeps reusing token and two different exchanges might be using same exchange token. It is not guaranteed to be unique.
I think that is very difficult to solve because on the client machine it is disconnected. I think it is better to check why it is getting disconnected in the first place. One shouldn't block the thread that is receiving ticks.
If you have taken care…
Are you sure you are disconnecting properly? It could be because you have not closed the connection at your end but server has an active state at its end and hence you are getting too many requests.
Add on subscription will be active but you will only be able to use it if you have base subscription. If you subscribe for Kite Connect, you can use historical data API till 28th June 2024.
Pi is not available anymore. You will have to use Kite Connect APIs for everything. If you are developing a product for mass then we suggest speaking to compliance team by writing to kiteconnect(at)zerodha.com
You shouldn't block the main thread that is receiving ticks. If you block the thread that is receiving ticks then you may miss the data. We subscribe to 100 of ticks at a time on our apps, we haven't encountered this issue.
A pop up is shown for confirmation that a debit of 2k will be posted in the account while subscribing for Kite Connect app. Users are expected to type "I understand" and not just a button click.
If you have deleted app by mistake, you can write to …