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.
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…
