We haven't encountered any issues on our end. Could you let us know how frequently you experience this error? Additionally, please enable debug logs in PyKiteConnect and share the complete stack trace with us. Be sure to remove any app and client-sp…
Kite Connect is purely an execution platform. I am afraid we can't provide support for writing code. You may refer to our GitHub repo to know more details.
should i create a thread of my own and run websocket in the main thread only or should i run the websocket in diff background thread and my main thread run on its own
You can run the WebSocket either in the main thread or in a background (daemon) th…
This issue doesn’t seem to be related to the Kite Connect itself. It’s likely due to something in the local setup, so a bit of trial and error will help narrow it down.
You could try temporarily disabling any antivirus or security software (other …
When you request historical candle data via the API, it's important to understand how the from and to parameters work. The to parameter sets the end of the time range you're interested in, but it doesn't specifically refer to the closing time of any…
I attempted to fetch historical data via the API, and it appears to match the NSE bhavcopy accurately. I recommend reviewing your code logic to identify and address any issues.
There are two ways to pass tick data from on_tick thread to perform any operation without blocking the main on_ticks thread. You may refer to this discussion for more details.
You can subscribe to up to 3000 instruments in a WebSocket connection. The number of ticks that you receive depends on the subscription mode; refer to this discussion here for more details.
Also, this could happen if you are blocking the ticker(wh…
If you’ve retrieved today's candle data on the same day, the OHLC data will not match the bhavcopy. This is because the OHLC updates through the bhavcopy occur at midnight. Therefore, starting the next morning, the day's OHLC in the bhavcopy and the…
Could you please provide the exact instrument details to check further? We want to determine if this issue is related to a specific instrument or affects all NIFTY options instruments, or applies to all instruments where you noticed missing ticks. A…
We receive a Unix timestamp in seconds from the exchange, which we convert to a Date object before passing it on to our clients. The exchange doesn't provide a timestamp in milliseconds, so we depend on the data they supply. However, you might consi…
@gs3141 In the WebSocket, OHLC reflects the values for the day's time frame (not for minute or hourly intervals). Once the market opens, the closing price will still represent the previous trading day, as the day's closing price is available only af…
In the WebSocket, OHLC represents the values for the day. Before the market opens, this data reflects the previous trading day's values. However, once the market opens, the closing price will still represent the previous trading day, while the openi…
We're checking this and will provide an update shortly. Meanwhile, kindly let us know whether you're facing this issue during any specific timeframe or it happens randomly.
Currently, we don't have a specific ETA for this. However, if you'd like to utilize the market protection feature, you can do so through a raw HTTP call for the time being.
Kite Connect is an execution platform. I am afraid we can't provide support for writing code. However, you might consider enabling debug logs for JavaKiteConnect or printing the KiteException message to understand the reason behind it.
Please note …
The input exception represents missing required fields, bad values for parameters, etc. You may refer to the documentation, sample code, and make the API request with the correct parameters.
To resolve the issue, you might consider enabling debug l…
No, you can't get the historical tick data for the day. You may refer to the documentation to know the available intervals/timeframes in historical data.
Kite Connect API does not offer historical tick data. You may refer to the documentation to know the available intervals/timeframes in historical data.
The above-mentioned instrument token for UNIMECH(NSE segment) seems incorrect. You may download the latest instrument file and check. Further, Instruments are identified by the exchange:tradingsymbol in the Quote API. You may get more details here.
The correct approach to subscribe to a large set of tokens (recommended batch size / delay).
If there are restrictions on subscription order or maximum tokens per batch.
You may refer to the documentation to know the limits.
Whether this error sugg…
do i need to login daily to get access token
This is done as per the exchange regulations. You need to login to the trading terminal every trading day. Go through the FAQs here.
can't i regenerate it with refresh token A refresh_token is provided on…
It is not guaranteed that a minute candle will be available at the end of the minute or at the beginning of the next minute.
I would suggest generating a candle at your end using the live market data provided by Kite Ticker. You may refer to a simi…
You can write to the business team explaining the issue, and they will check and get back to you. You can reach out to them on kiteconnect(at)zerodha.com.
You'll need to use the opposite transaction type. For instance, if you have a buy/long position, your transaction type should be sell, and if you have a sell/short position, it should be buy.
1. Do we currently have a paid plan active?
Currently, there is no active paid app.
we've paid already on the portal, but not sure as the API key appears to be still free
2. Ask them the URL of billing page where you can check the active plan and up…
The difference between the initial/required margin and the final margin reflects the benefits of the spread. If the final margin (total_field) is positive, it represents the margin blocked for the basket orders post-execution. Conversely, if the fin…
Is Iceberg provision not available in API?
You can place iceberg orders via API. You may refer to the sample here.
Can you advise what fool proof or backup mechanism are followed by season algo traders to ensure, exits are FAIL PROOF
Kite Connect is…
Based on the attached screenshot, it appears that the request token is present in the URL. You can use this token to obtain the access token. For additional information, please refer to the documentation.
It looks like the API key you mentioned earlier is associated with the free version. If you've set up a Kite Connect (paid version) app, you can use the API key and access token from that paid version app to resolve the issue.
Please avoid sharing your API key, access token, and client and app specific details publicly. I've removed it for you this time. Additionally, market data cannot be accessed via WebSocket with the Kite Connect personal app (free version), which is …
During the pre-market session for the first 8 minutes, i.e. between 9:00 AM and 9:08 AM, orders are collected, modified, or cancelled by the exchange. The order collection window can close at any time between 9:07 AM and 9:08 AM. The orders placed a…
Rather than checking the margin for each order separately, you can easily check the combined margins by including both orders in the basket order API as a single request. This approach will provide you with the net margin requirement details. Additi…
It's important to note that there isn't a guaranteed availability of a minute candle precisely at the end of one minute or the start of the next.
Our historical data service captures the ticks within a minute and then generates a candle from this …
The Postback API is designed to send notifications only for orders placed using the app’s specific API key. You may refer to the documentation for more details.
To identify the exact issue, you’ll need to capture the raw error response from the order placement API request. The error remarks there will give more clarity, based on which you can investigate further and work toward resolving it.
Tick-by-tick data is typically used by professional high-frequency and arbitrage trading firms. For most retail traders, it may not offer much practical benefit. You may refer to this post for more details.
However, KiteConnect is not meant for HF…
@Walker, I fetched the historical data for the security you mentioned and didn't find any discrepancies between the historical data and the Kite candle. I recommend trying it again on your end. Please note that both the historical data and the Kite …
To assist you more effectively, could you please provide the following details: the HTTP method used (such as POST, PUT, or GET), the endpoints accessed, the parameters used, and the complete error response received when the issue occurred?
You can…
Kite Connect primarily serves as an execution platform, and while we do our best to provide valuable data, we are not a comprehensive data vendor. For detailed information on unlisted instruments, we recommend reaching out to an exchange-registered …
Currently, there's no official endpoint that allows you to retrieve the entire transaction history for a mutual fund. However, you can access a list of all mutual fund orders, both open and executed, from the last 7 days using this endpoint. For mor…
https://api.kite.trade/mf/holdings/{tradingsymbol}
The endpoint you mentioned isn't part of the official ones listed in the documentation. You might want to use the official endpoint (/mf/holdings) to retrieve the list of mutual fund holdings availa…
To get Friday's closing price, you would need to fetch it on the next working day—Monday. You might want to try retrieving the close price now; it should match up.
I used getMargins, function, and everything seems to be working fine. You might want to try it again on your end. If the issue still occurs, you could enable debug mode to identify and resolve the problem.
We don't have any limit on the number of instruments that can be added per request for the margin calculation API, but there is a max payload cap of around 100 kB
The timeline for implementation of SEBI circular SEBI/HO/MIRSD/MIRSD-PoD/P/CIR/2025/0000013 on "Safer participation of retail investors in Algorithmic trading" has been extended from August 1, 2025 to October 1, 2025. You may refer to the circular f…
Could you please share the complete stack trace/error details via private message? Additionally, are you able to make requests to any other API through the proxy?
1. You may refer to the similar discussion here
2. I reviewed both the historical API data and the Kite web, and they match. You may fetch the data again and cross-verify it.
1. What is the reason for the mismatched data from kite web and api?
The Kite web and historical API responses should match. If you encounter any instances where the details do not align, please share the raw API response and a screenshot of Kite we…
You won't receive data if the instrument token is incorrect. I recommend fetching the correct instrument token from the instrument file and cross-verifying to ensure you're subscribing to the correct one.
@jaimin_blackqr We haven't made any changes on our end. It's possible that some ticks were missed due to latency or connectivity issues.
Additionally, we use the same tick data to form OHLCV candles as displayed on the Kite charts, so unless you a…
do I need to say no modify only for remaining quantity which is pendingQuantity?
When you modify an order without the quantity field, the updated criteria will apply to the pending quantity.
Also in the process of modifying if I get the fill how is …
It doesn't have to match exactly because both have different sources. If you need accurate tick-by-tick data, you need to be at the exchange in a colocation server, which costs 20+ lakhs per annum.
Please check out this thread for more information.
For NIFTY and SENSEX, it is not possible to get the same-day close via the Kite Connect API at the moment. However, you can retrieve the closing price data the next morning on the following working day. Both the Quote and Historical API calls should…
For GIFT NIFTY, there is a difference because the historical API data provides the LTP as the close price, and currently, there isn't a separate process to update the closing price. Typically, historical OHLC data can be obtained via the historical …
The charting engine's ticker source is different from the Websocket API's source. Quote endpoint would provide only market data snapshots. You might find this thread helpful for understanding the inconsistencies in chart data.
Additionally, you can…
If you have multiple Zerodha accounts and are logged into a different account on the browser that you're using for your OAuth-based login, this error may occur.
If you only have one Zerodha account, please navigate to the app details screen to veri…
Please ensure that you are entering the correct API key without any extra spaces. You might find this similar discussion helpful.
Additionally, remember that there's no need to generate a request token and access token every time. Once you have an …
Can you enable the debug logs of kiteconnectjs and the complete stack trace here?
You can enable debug logs as mentioned here.
PS: Make sure to remove app and client-specific tokens while pasting here.
It seems that the condition you're attempting to modify has already been met.
When modifying the GTT details, you would have to send the last_price based on the current LTP. Could you please check if you're sending the correct LTP when modifying t…
Is it possible to retrieve available Leverage data for a given scrip?
You can use this endpoint to fetch margin details for MTF(product parameter = MTF).
Also currently get holdings API does not return if the holding is MTF or not.
Holding API respo…
Navigate to the app details screen and check if you have entered the correct client ID. Ensure there are no spaces at the beginning or end of the client ID. You must use the Kite Connect APIs with the same client ID that you used to create the app. …
If i wanted the net qty, i would add the day's positions to the holdings, right ?
You may refer to the response structure which would have fields "net" and "day" in the documentation.
But there are different behaviors for BUY and SELL.
I bought XXX …
Kite Ticker expects valid credentials for connecting to the ticker. If you see a '403' error, then it means either api_key is invalid or the access token is invalid. You may go the similar discussion here.
