If you've created two Kite Connect apps, you can place up to 10 orders per second(per segment per exchange) in each app.
Correcting @Nivas here. This isn't right. One can only have one API key with 10 orders per second per exchange per segment. The …
@akhilesh_singla icebergs are an algo in themselves, we have approval for iceberg orders as an algo. We'll have to see how the orders are counted, this isn't defined yet.
If the accounts belong to your immediate family, the same IP will do. If they're not immediate family, they'll need separate IPs. The 10 OPS limit is per API key.
@ANL @sahilMn I agree with you on the need for having everyone heard, but there are limits to what we can get done. There was an extensive consultation process before these norms were published, and these concerns were indeed aired at the time. Howe…
Service providers who send trades on behalf of customers are the targets of this regulation. The idea is to not allow for such actors. If you want to send trades on behalf of others, you'll need to get yourself and your strategies approved as vendor…
@akshtgt anywhere except Pakistan, Democratic People's Republic of Korea (DPRK), Iran and Myanmar will work.
@sahilMn There was an extensive consultative process. This is the best possible outcome. The alternative was no APIs.
How will this be implemented? Will it be tied to API key such that all orders emanating from any algo that makes use of a particular API key will have the same Algo ID assigned to them all?
Yes, that is the plan for now. If the exchanges propose a d…
@Karimbaig5 please write to [email protected] and someone will help you out.
@boobeshwari unfortunately, this is the best case scenario. The regulator is not comfortable allowing APIs without the static IP constraint.
1. How a trader can deploy his algo on AWS or any cloud service without getting IP overhead.
There will be some overhead. Unavoidable.
2. How does a trader overcome issues when he is travelling and runs his algo in different places?
This is up to th…
@donisback you'll need a static IP regardless of order rate, yes. The static IP will only be for the order place/modify/cancel endpoints.
@kkzooms we have a no refund policy. It becomes very difficult to do any downward revision of pricing if we're…
Hey. Personal doesn't come with data, real time or historical. This thread was created before Personal was announced. Free historical data is only available with Kite Connect.
@whity this token saved in the text file is for the same day or reused everyday? An access token is only valid for the current trading day and you'll have to generate a new one everyday.
Hey, this isn't available on Kite Connect yet. Primarily because the auction market doesn't open at the same time consistently, and the instruments are only published after the markets open. We're working on handling these quirks before we make this…
Hey @krishkalyani @amman777, it isn't scalable to offer data for free. There is a cost to maintaining the infrastructure to offer these APIs and data is quite a large part of that cost.
The OAuth wouldn't work from your home PC's IP since it would be different from the one attached to your app, so this wouldn't work.
I was wrong. Login from home IP and everything else from server should work too.
Fintech vendors will have vendor APIs where this will not be a problem. This static IP/client IP problem won't exist in that setup. The controls for vendors are different.
If anyone has made is custom trading platform for "manual trading". Even that…
Kite Connect is a suite of execution APIs that we are allowed to offer as brokers. A data-only API would require us to be data vendors, which we are not.
@namratasonawane all these concerns were discussed with the regulator. After a lot of back and forth, this was the least painful solution. The most painful being just all APIs being disallowed.
You'll have to use a service with a static IP. If the frequency of change in IP isn't too high, you can manually update it. Allowing change of IP with an API is not something I think is in the spirit of this regulation.
We stopped allowing order placement for MFs from Kite Connect when the orders needed payment to happen from the users' bank account, back in 2020. We'll update the documentation and remove these endpoints to prevent confusion.
Hey @maxhiten, I manage the team that handles such queries and requests at Zerodha (the compliance team behind kiteconnect(at)zerodha.com). It would be best if you write to this channel since it is our team's job to evaluate such projects. :-)
Nope. Priority is time-based. Order that hits the exchange orderbook first is validated first, if it can be filled, it is. If not, IOC gets cancelled and DAY gets entered into the depth and waits for fill.
No problem. I think there is a misunderstanding of the semantics here. IOC is the order validity. The type is still limit. So while the order is valid for a very short amount of time, the nature of the order and the price parameters used to match it…
This is in the nature of limit orders. The matching engine sees that you're offering to pay 135 rupees for a stock worth 130, which means you shouldn't mind the 5 rupee discount, so your order is filled at the best price available, which is better t…
xclude it entirely, while feeding into technical indicators
Yep, this is best practice.
form candles from ticks on your own is not a good one either, as you are not guaranteed to receive all the ticks of high volume scrips.
This isn't any different …
I don't get the logic. Why does the regulator need the user's IP address if he doesn't want to place an order? Data analysis and order placement are totally different. Data analysing, we do the computation with our PC, which is very private and does…
Have discussed this here: https://tradingqna.com/t/query-on-future-of-apis-for-traders/160288/52?u=matti
Basically, this circular distinguishes between algo orders and API orders. If the order rates are within a prescribed order-per-unit-time thres…
We've also emailed all the affected users with this information. So if you're wondering if this applies to you,
1. Check if your app was supposed to expire in the past 10 days.
2. If you're still unsure if this is relevant to you, check your email.
Yes, your app wouldn't have those permissions. This would have been explained before when your app was created. Best write to the business team on kiteconnect[at]zerodha[dot]com if there's a confusion regarding this.
This only talks about giving PoA for the demat account. The demat account is where your shares are stored. The transactions happen on the broker account. The demat account is attached to this broker account.
No, the Kite Connect terms of use clearly define the way data obtained from the APIs can be used. Violation of these terms leads to suspension of the account. This covers users.
Are you talking about kite connect websocket or kite charts? When you say that there are different sources of data feed, aren't we supposed to get feed (on websocket) only from 1 source which is meant for market participants?
What Faisal means is th…
This actually comes from point 6.c here. We're required to ensure that there's some session timeout. We use 1 day for this, but it could be shorter too.
Ah. @MAG @tradernoob I was wrong. My bad. This hasn't gone live yet. Here's the NSE circular: https://nsearchives.nseindia.com/content/circulars/MSD60724.pdf
This will only take effect in April.
Any idea why u started validating the quantity parameter which was optional to modify_order?
This change was meant for order placements. The validation on order_modify was an unintended side-effect.
Kite Team just makes the changes overnight without any announcement. It would be great, If you notify the users at least 24 hours before making the changes. 1 week would be better, but 24 hours is at least required!
You're right that we're expected …
It would be premature to speculate about this right now. This is being discussed with the regulator. The MC article is vague because that's just how much we know today. The final decision is yet to be made.
Hey @tradernoob, sorry for the late reply. As Sujith said earlier, we simply relay ticks that we receive as is. Any additional fields you've mentioned aren't available over our WS, but that isn't an indicator of any processing of ticks.
Answering this here for the benefit of anyone else who may have similar questions. The data from Kite Connect is for personal consumption only. For commercial purposes, one should purchase data from an exchange authorised data vendor.
There are no contradictions, Gautam. The documentation does not need to describe non-technical elements that you interact with when using the APIs. Also, usage of the APIs is contingent on knowing the underlying platform.
Your ask of having all of …
Hey Gautam, no Zerodha representative would want to offend a paying customer (or anybody else!).
When @sujith pointed out topics to understand definitions of terms like CNC/NRML, or how to determine if a position is long or short, or what Average T…
Since we don't offer algos as a service, and all orders on Kite Connect are subject to the same risk management checks as all other orders from Kite, this doesn't apply to orders from Kite Connect.
This circular is for people having algos regi…
Hi @Kirubhakaran, as it stands, we no longer offer this service. Even in the past, our colo service was quite barebones, since it is operationally quite complex to offer.
Hey. Scraping isn't allowed. If you're found to be scraping, you'd be using Kite in a manner that it wasn't intended to be and you'd stand in violation of the terms of service.
Hey @gaurmmec, this was an issue at the exchange. Check out this post on our bulletin: https://zerodha.com/marketintel/bulletin/309977/exchange-order-execution-issue-resolved
@JeetKumar if you lose or change your phone, clicking on the forgot password link will allow you to reset the 2FA and login. You can then set up a new TOTP.
I was reading your previous post and you're right about the fact that this rule is in p…
Hi @JeetKumar
We understand the situation and can sympathise with your plight. However, we can't make an exception to complying with SEBI rules. SEBI is going to mandate 2FA for all the platforms across the brokers soon.
@narayanan, as I say in my original post making the announcement, this does not involve any changes to the APIs and does not require any changes to your code. You simply need to enable TOTP on your Zerodha account. Functionally, the APIs remain unch…
@neerleo88 this was always available as an optional feature. The change is that we're mandating it now, and perhaps soon for all other platforms as well.
