This error is not related to the Kite Connect API. However, it requires a thorough investigation. We recommend raising a ticket on the support portal with the complete details for further assistance.
We haven’t observed any issues with the WebSocket during that period. If you do experience any issues in the future, please share the error details along with the corresponding timestamp, and we’ll review them and assist you further.
Timeouts can occur for several reasons, such as network or ISP connectivity issues. They may also happen if requests are sent too frequently or concurrently beyond the allowed rate limits, which can cause temporary blocking at the CDN level.
The ping fails because Kite's WebSocket server intentionally blocks ICMP ping requests for security reasons (DDoS prevention).
Ping uses ICMP protocol (blocked)
WebSocket uses TCP protocol (allowed)
As long as your WebSocket connects and rece…
A small subset of connections experienced this issue again. Our technical team is treating this with high priority and is actively working on it. While we had earlier implemented preventive measures, we’re now strengthening them further to ensure im…
A small subset of connections experienced this issue again. Our technical team is treating this with high priority and is actively working on it. While we had earlier implemented preventive measures, we’re now strengthening them further to ensure im…
A small subset of connections experienced this issue again. Our technical team is treating this with high priority and is actively working on it. While we had earlier implemented preventive measures, we’re now strengthening them further to ensure im…
A small subset of connections experienced this issue again. Our technical team is treating this with high priority and is actively working on it. While we had earlier implemented preventive measures, we’re now strengthening them further to ensure im…
This does not appear to be a Kite Connect issue. Please share the API endpoints you are using along with the actual API error response so we can review and assist you further.
If the issue persists, enable debug mode and share the complete stack tr…
@KamalChhirang A limited number of connections experienced this error. We've conducted a thorough investigation, and the necessary changes will be implemented to prevent this from recurring.
A limited number of connections experienced this error. We've conducted a thorough investigation, and the necessary changes will be implemented to prevent this from recurring.
We have not observed any issues on our end. Could you please confirm whether the 503 error occurred only before market opening, and whether it was a recurring issue or resolved upon retry?
@Shriismyname At present, the last price for mutual funds may be subject to a slight delay. However, we would like to assure you that upcoming updates are planned to ensure the latest data is reflected.
This is not a Kite Connect error. The message request failed (SSLServerVerification) indicates a local SSL/TLS verification failure on your system while establishing an HTTPS connection. The request does not reach Kite servers.
This may happen due …
Fetching the masters once after around 8:30 AM is recommended.
While this is expected to remain stable going forward, in case you notice any discrepancies, please update this thread, and we will review it accordingly.
We observed that File 2 stopped recording at 11:28 PM, which accounts for some of the discrepancy compared to File 1.
Beyond the recording time, it’s important to note that WebSocket connections function independently. Since the ticker provides the…
There was an intermittent issue with Kite Ticker in the morning wherein ticks were freezing. We had done some changes to fix it and restarted the service. You might have observed the error response at that time. It should be resolved now.
I've remo…
Since these securities have zero volume, the exchange is sending a consistent, unchanging tick throughout the day. We will check and notify the exchange about this pattern.
Kite Ticker publishes whatever data is published by the exchange. We don't …
The Kite Connect documentation is currently up to date. The parameters `Squareoff` and `TrailingStoploss` are not supported in the Kite Connect API at this time, and hence are not documented.
These fields appear in the Go client as part of legacy o…
For older historical data, the records have been curated from multiple data vendors, and as a result, you may notice some variations in how timestamps are represented for daily candles.
Since these are daily candles, the timestamp serves as a date …
It isn’t possible to share an expected tick count for a trading day, as tick generation is event-driven and varies with liquidity and market activity.
Kite’s WebSocket provides snapshot-based market data, so there is no deterministic way to verify …
The Kite Connect Java SDK is working correctly. The error occurs because the JAR is not on the classpath during compilation, or the JAR file is invalid/corrupted.
To verify the JAR file integrity:
jar tf kiteconnect.jar
If you can't see the conte…
Through Kite WebSocket, you can receive live market data, including Open Interest (OI). To track exactly when the OI was recorded, you can refer to the exchange timestamp provided within the WebSocket response.
Additionally, for liquid instruments,…
This could be because of the non-JSON response from the server, like when a Cloudflare error is thrown.
You can catch the exception and retry.
You may add delays between API calls to respect rate limits (Kite's quote API allows 1 request/second)
The error response you provided does not match the official Kite Connect format, which can be found in our documentation here.
It appears likely that either your codebase is intercepting the Kite Connect error and printing its own custom exception,…
I have tested placing async orders on my end and did not encounter any delays. Therefore, it appears this issue is not originating within the Kite Connect API.
As Kite Connect is an execution platform, we are unable to offer support or debugging as…
Generally, a stray tick wouldn't be sent in the pre-market hours. However, Kite Ticker sends the last stored cached tick the first time when the user subscribes to a token. Post that a tick is sent only when there is a change in any of the values. Y…
These interactions are not Direct Messages (DMs); rather, they are comments posted publicly as an Activity on a user's profile.
Please note that if the moderators ever require confidential or sensitive information to investigate an issue further, t…
I could not find any error specifically related to Kite Connect. It appears the issue is originating within your codebase.
Kite Connect is purely an execution platform. While we are always happy to provide support and troubleshooting for any direct…
@dinezh If you are using the Kite Connect paid version, you can use Websockets to get order updates. If you are using the Kite Connect free version, you have to use Postback/Webhook to get order updates.
@dinezh For individual developers, WebSocket is recommended, where orders placed for a particular user anywhere, for instance, web, mobile, or desktop platforms, are sent.
@ttsdev We’ve reviewed the postback update and noticed that the first modification is being received, but it’s reflecting the original order price rather than the modified price.
To get the latest details, you can use the postback message as a trig…
Kite Connect Login flow doesn't have any issues, and this error isn't related to the Kite Connect. Further, it is mandatory by the exchange that a user has to log in manually at least once a day. We don't recommend automating the Kite Connect login.
We've conducted tests by submitting multiple API requests across different time frames, and we haven't been able to replicate the delay you're seeing. Since Kite Connect is leveraged by a vast number of users and platforms, a server-side issue would…
1. There have been no known issues or maintenance activities in the past few days.
2. The KiteTicker library supports automatic reconnection when setTryReconnection(true) is enabled, so you don’t need to manually call connect() after every disconnec…
1. The continuous futures chart categorizes all historical futures contracts into current, near, and far months. So when you fetch a current month historical chart, it pulls data from all current months historically. Similarly, when you fetch a near…
@khatumaaibani There are three modes in the WebSocket subscription; you may refer to the documentation, and let us know the WebSocket subscription mode.
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 …
