I have added the market_protection field , but started getting error this morning as of Mar-27.
KiteConnect.place_order() got an unexpected keyword argument 'market_protection'
@adarsh1392 At present, market protection is supported in the raw HTTP A…
Can i still tradethrough tradetron or algotest like platforms , with a static ip from them
@saimathew You must ensure that orders are routed through a whitelisted static IP.
Is placing orders via a proxy IP allowed?
@shan1326 For API-based order pl…
that I know, the thing that I am asking is each app that is created, the charges will be debited from each account or one single account, for example currently I have 3 seperate developer accounts, and charges are debited from there accounts i.e 500…
Try the following:
Add a slight delay between API calls to avoid burst requests
Log and verify the exact number of instruments being sent in each request (based on debug logs)
Reduce the number of instruments per request (e.g., try with 100–200)…
will the charges be deducted from a single developer account or from other respective accounts after creating different apps?
@Tusshar18 There are two ways to make payments for Kite Connect paid apps. You can either link your Zerodha account on the …
It’s not really about whether you use Selenium or a Chrome extension. What matters is how you’re interacting with the platform.
If the approach involves scraping or bypassing intended access methods instead of using the officially supported APIs, i…
There was a change in the expiry date for Copper March options contracts from 24th March 2026 to 23rd March 2026. The instrument file has the correct expiry date.
Currently, there is no official API support for managing watchlists via Kite Connect. The available APIs are primarily designed for order placement, market data access, and portfolio-related operations.
Regarding the use of Selenium or similar tool…
@tuxred No, the session will not be the same for your app and your wife’s app.
Each session is created using:
The API key/secret of a specific app
The login of the corresponding client ID
So, even if both apps are under the same Kite Connect de…
@tuxred Under a single Kite Connect developer account, you can create multiple apps, and each app can be mapped to a different client ID.
While creating an app, you will be asked to provide the client ID. This means:
You can create one app using …
@yogeshs Please refer to this Exchange Circular for more information. It contains a reference to the relevant SEBI circular if you'd like to look into the finer details.
The quote endpoint is rate-limited (~1 request per second). If requests are made in quick succession or in parallel, this can lead to intermittent failures even with valid inputs.
To help us investigate further, please enable debug logging and share…
so for now, do we have to use different IPs for family account ,??
We’ve updated the terms for Kite Connect regarding static IP sharing; please see the screenshot below for the specific details.
If you'd like to share a static IP with family membe…
If my orders are not exceeding 10 per second, do i still need a static ip to the api key ?
Static is mandatory for the orders endpoint regardless of order count(i.e., 10 OPS)
At the moment, our Mutual Fund endpoints are limited to the GET method, so PUT and POST requests aren't currently supported. We’ve noted your feedback and will share it with the relevant team for future consideration.
While the symptoms mirrored previous incidents, root-cause analysis showed no link to those events. Remediation has been completed, and safeguards have been added to help ensure it does not recur.
Although both the Kite chart data and Kite Connect Websocket data originate from the same underlying stream, they are delivered through two separate WebSocket connections. Because of this architectural design, slight differences in the ticks receive…
The issue reported today is not related to the previous incident, which had already been resolved. Earlier today, we encountered a rare edge case that briefly triggered this behavior. The necessary changes have been implemented, and we do not expect…
@manisatya009 @rs20375 This enhancement is currently in our development pipeline for a future SDK release. Until then, we suggest utilizing the HTTP API directly, which will allow you to implement this functionality immediately.
Since the request is receiving a 400 response from the AWS (awselb/2.0) rather than a WebSocket protocol or authentication error, the connection is likely being rejected during the initial handshake phase before reaching the Kite WebSocket service.
…
Could you please verify whether the WebSocket handshake headers are being sent correctly, especially if you are using a lower-level WebSocket client that performs a minimal handshake? In some cases, differences in client handshake behavior can lead …
With the paid version of Kite Connect, access includes live market data, historical data endpoints, as well as order-related endpoints as part of a single offering.
From a security standpoint, this does not inherently create additional risk, as ac…
Kite Connect currently focuses on trading-specific APIs and does not offer back-office features. As a result, we are unable to provide a dedicated API for the 'kill switch' at this time.
which is why i'm asking what's the max delay.
The timing of these updates can fluctuate depending on certain factors. As a result, we aren't able to provide a definitive timeframe for the delay.
Timeouts can occur for several reasons, such as network, firewall, 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 lev…
It's not recommended to poll position APIs to fetch last_price; it gets updated arbitrarily with a slight delay. It is thus not possible to provide accurate, real-time P&L with an HTTP response, and the recommended way is to use WebSockets/quote…
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.
