In Kite Connect, multiple API keys cannot share the same API secret, a single access token cannot be used across different applications, and each app has its own API key, API secret, and session, with the generate_session process being specific to e…
You currently have a Personal app active in your developer account, along with 500 available credits. To fetch live and historical data, please use these credits to create an app in the Connect section.
The API response data will be empty if the instrument identifier is not passed correctly. Please ensure that the instrument identifier is provided accurately to avoid this issue.
It appears that an incorrect client ID has been entered in the Zerodha Client ID section of your developer account. Kindly update it with the correct client ID in the app section and try again. You may also refer to similar discussions.
@tuxred This provision hasn't been integrated into the developer dashboard just yet. However, it is high on our priority list, and we expect it to be added in the very near future.
We have limitations to fetch historical data
"minute": 30,
"hour": 365,
"day": 2000,
"3minute": 90,
"5minute": 90,
"10minute": 90,
"15minute": 180,
"30minute": 180,
"60minute": 365
You can fetch complete historic…
Verified this and found that there has been a corporate action (dividend) for the MRPL scrip.Kite displays the adjusted price after accounting for the dividend, whereas platforms like TradingView and others may show the unadjusted price.
The ticks may not have been broadcast due to the thread being blocked, as mentioned earlier. Even after refactoring this implementation, there is still a possibility that not all ticks will be captured.
Because when viewing a 1-minute chart, thousan…
Navigate to the app details screen and verify that you have entered the correct client ID. Ensure there are no spaces at the beginning or end of the client ID. The Kite Connect APIs must be used with the same client ID that was used to create the ap…
When the WebSocket thread is blocked, some ticks may be lost and cannot be retrieved later. Splitting tokens across 2–3 WebSocket connections does not guarantee that you will receive more ticks.
Please note that the data received for the Kite chart…
We see that you have an active connect app in your developer account. If you have any concerns, please feel free to write to us directly to [email protected].
You are not permitted to access or operate another user’s Zerodha account, even with their explicit consent. If you are building a platform for mass retail users, you may write directly to [email protected] with complete details about your pla…
You need to scroll down to view the Zerodha Client ID section and verify that the correct ID is mentioned. Ensure there are no spaces at the beginning or end of the client ID.For further clarification, you may refer to this similar discussion.
A valid access token is required to connect to Kite Ticker. It appears that either the API key or the access token being passed is invalid. Kindly generate a new access token as mentioned in the documentation. You may refer to this forum discussio…
The Kite Ticker requires valid credentials. If you receive a 403 error, it means the api_key or access_token is invalid. Please refer to this discussion.
NIFTY futures expire on the last Tuesday of every month. You may refer to the provided link for further details.
There are no API endpoints available to fetch information on expired historical contracts. This data can be obtained directly from the …
Please ensure you are entering the correct API key without any extra spaces. You might find this similar discussion helpful. For more details, please refer to the documentation.
To understand the continuous=True parameter in more detail, refer to the official documentation.
Please note that the OHLC values will not be identical to those of individual futures contracts. Continuous futures charts aggregate historical data ac…
If you require the OHLC data of the most recent intraday candle, the WebSocket connection must be used, as there are no alternative methods available.
If you require day-level OHLC data, the Quotes API can be used for this purpose.
We have passed on this issue to the concerned team. The recommended workaround is to use the postback message as a trigger to fetch the order book and verify the latest details. Alternatively, you may fetch the order history and review the most rece…
The Kite Connect instruments file provides only a complete data dump. You will need to filter and extract the required information from this file based on your use case.
Kite Connect APIs currently only supports trading platform APIs and does not provide back-office data. To access tradebook, ledger, and other reports, please download them from the Zerodha Console.
We may include them in the future.
Yes, we have limitations to fetch historical data
"minute": 30,
"hour": 365,
"day": 2000,
"3minute": 90,
"5minute": 90,
"10minute": 90,
"15minute": 180,
"30minute": 180,
"60minute": 365
You can fetch complete historical data by making multiple requ…
The call ltp_data = kite.ltp([f"{exchange}:{tradingsymbol}"]) has triggered a permission issue. If you wish to fetch LTP and place GTT orders, you can opt for the paid version of the API, i.e., the Connect API.
With the Kite Connect Personal app, it's not possible to access real-time or historical market data. For more details, you might find this thread helpful.
Indices are not exchange-traded securities. As such, they do not have actual trade volume since the index itself cannot be directly bought or sold on the NSE. You may refer to this similar discussion for more details.
If you have created multiple apps, please ensure that you're using the API key and access token for the Connect app (paid version), rather than the Personal app (free version). This issue typically arises when the credentials from the Personal app a…
We do not provide historical data for expired option instruments. Historical data is available only for expired futures instruments, and that too limited to day-level candles.
As an alternative, you may set up a WebSocket connection to capture and s…
For an odd lot of 31 lots, the first leg will be placed as 16 × 65, and the second leg as 15 × 65. The quantity is rounded up as per the formula below:
s = quantity / max(legCount, 2)
iceberg_quantity = ceil(s / lotSize) × lotSize
You may refer t…
A user can trade only in instruments that are available in the Kite Connect instruments dump. All the required instrument details can be obtained from the instruments dump itself.
With the Kite Connect Personal app, it's not possible to access real-time or historical market data.
If you have created multiple apps, please ensure that you're using the API key and access token for the Connect app (paid version), rather than the …
There is no direct API endpoint or stream available to fetch the option chain. You will need to build it on your end by filtering the instruments and retrieving OI, LTP, and volume using either the WebSocket stream or the Quote APIs, based on your r…
Navigate to the app details screen and verify that you have entered the correct client ID. Ensure there are no spaces at the beginning or end of the client ID. The Kite Connect APIs must be used with the same client ID that was used to create the ap…
Currently, tags are not supported in GTT and are available only for order placement. However, we’ve shared this feedback with our team and will check the feasibility.
Kite Connect is purely an execution platform and we don't provide support for coding. You may refer to our API documentation and github resources for coding assistance.
You can use the web console and the API simultaneously. For the smooth experience, we recommend this flow:
1: Generate the access token using the API.
2: Then, log in to the Kite Web/console web. Following these steps ensures you won't be logged out…
The above error is due to Cloudflare block, you may check out this support article to resolve this error. You may also check out the documentation for more help.
TotalBuy and TotalSell are legacy variables that were added to Go Kite Connect a long time ago and are not actively used. The Kite Connect API does not include these fields; they exist only as unused variables in the Go library. We will remove them …
