Only order collection happens from 09:00 AM to 09:07 AM, and when an equilibrium price is achieved at 09:08 AM, an LTP is published. The behavior on Kite web and Websocket API are same.
Monthly expiry is on 25th October 2024 (SENSEX24OCT80200PE) and the weekly expiry is on 31st October 2024 (SENSEX24O3180200PE)
You need to look at the tradingsymbol format and figure out which one is monthly and weekly expiry.
You can know more abou…
The Kite Connect app is provided only for personal use. It can't be used with any other client id. You need to use the app with the client id that was entered while creating the Kite Connect app.
The historical data API is only meant for backesting purposes only. We suggest generating candles at your end for live market strategies.
You may get started from here.
Can you mention which endpoint you are referring to? How you are searching, example tradingsymbol?
Please note that from November 2024, many of the weekly expiry instruments are being discontinued. You can refer to the bulletin here.
There are few edge cases wherein order updates are received twice. The solution is to use this as an event to fetch orderbook and look for the latest status of the order and filled quantity for partial fill. An UPDATE status could be partial fill or…
You place an order and wait for order updates on Websocket API. If you get disconnected or reconnected then fetch orderbook and check for the latest status of the order.
On order update, you can place OCO GTT for exit and keep modifying the required…
You should never generate symbol at your end. It may go wrong in production. One should always find the tradingsymbol from the instruments master which has all the symbols that are traded for the day.
How often do you fetch balance? Is it after every 10 minutes? At what time did you get the error?
Can you enable debug logs for pykiteconnect and share complete stack trace?
Maybe there was some backend process that was being run. Hence you didn't see the holdings. Both Kite web and API are powered by the same backend. It is not possible that on Kite web it is showing and at the same time on Kite Connect API, it is not …
A close price in a minute candle data is the last tick received in that minute by our system. The close price of the day candle data is usually updated the next day early morning, the value comes from the BHAV copy which is declared by the exchange …
Is this on the day, you took trade or the next trading session? Can you enable debug logs for pykiteconnect and share the complete request and response json?
Make sure to remove client and app specific tokens.
You can find all the instruments details that are traded for the day on the instruments master file.
In the above screenshot you seem to be using exchange and instrument token. The accepted input format is either instrument_token or exchange:instru…
The instruments master filed doesn't check for authentication. Hence you are able to fetch data without valid access token as well.
If you are getting 403 then you need to generate a new access token.
We haven't observed any issue at our end. Can you let us know how often do you see this and which endpoint is throwing this error?
Can you also share the complete stack trace with us by enabling debug logs of pykiteconnect?
Make sure to remove app a…
You might be getting blocked because of CDN. The solution is to use dump old candles at your end and use that as source and build candles at your end for live market data.
The historical data API is provided for backtesting purposes. It is not meant for live market strategies.
You can generate candles at your end using the live market data provided on Websocket API. You can check out this thread to know more.
You can go to developers console, go to billing section and buy credits or link Zerodha account for auto renewal. Go to My apps and then click on app you want to renew and then click on renew app button on the right section of the app details page. …
As you can see in the same thread, I have asked for the IP address on 25th of september and you haven't given that. How can someone help you out if there is no data for investigation.
Kite Connect is purely and execution platform. We don't provide one to one support for Kite Connect. There are no support agents here. We are all developers like you who work on our projects and take out some time to help fellow community members. Y…
You seem to the comparing two different instruments data. As you can see above, not only total buy/sell quantity is different but all other data points are also different. You can find the correct instrument token from the instruments master dump.
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 .
