You can only see separate entry on the orderbook as mentioned by you. Positions has no relation with orderbook, it is just a mark to market(m2m) of your account with respect to the market. One can't exit a particular order but can go long or short i…
It could be because CDN is thinking you are doing DDOS since you keep on requesting continuously, even when you get error. If you are polling HTTP endpoints every second then I would suggest using Websocket API.
32 byte packet is for index instruments. You might be using a wrong instrument token. You can fetch instruments master file and check the correct instrument token.
Kite Connect is purely an execution platform. We don't provide support or solution to write strategies.
If you are new to the programming concepts, there are many freelancers on the forum, you may hire anyone who is interested to help you out.
Only base subscription will expire. You will have to renew base subscription to use historical data API. The historical data API just requires base subscription to use but has independent subscription cycle.
Can you share the instrument token with which you are trying? There are three modes supported by Kite Ticker. You can check out the documentation to know more.
The values will be near but it won't match since the source snapshot data for the historical data is different.
You can read Nithin's answer in the above linked thread thoroughly to know more about the nuances .
I am afraid we can't add these fields since the source doesn't have these fields. You may have to listen to all ticks and create change in OI at your end.
Kite Connect only provides trading APIs and not the backoffice APIs. You will have to ask users to download trade data from console and upload it on your website.
Can you share the debug logs when it happens? You can enable debug flag while initializing pykiteconnect.
Make sure to remove app and client specific tokens while sharing logs here.
You need to place a stoploss order and not a limit order. You can check out the documentation to know more.
Kite Connect is purely an execution platform. We don't provide one to one support or solutions to write strategies. You can post your querie…
A holding is just an asset you are holding in your DEMAT. It is not associated with any of the exchanges. For ease of use and visualization, we show the holding based on one of the exchanges. You can read the article as mentioned above to know what …
One can create up to 3 Websocket API connection using one api_key. And each of these can support streaming for up to 3000 instruments. If you want more, you will have to create a new api_key and use that.
There is no co-relation between an orderbook and positions. Positions is just a means to see your mark to market whereas orderbook shows the list of orders placed by the client.
I am afraid we can't add tags for now. You can add it at your end.
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.
