If you have more than one Zerodha account & if you are already logged into a different account on the browser which you are using for your OAuth based login, then you will see this error.
Sometimes we do not realize it. On a new tab, open kite …
Thanks Matti!
Use-case 1:
That would be another blow. I think it is better if you get this point clarified. Normally if I have my website and it is being access by me via a browser. I am providing a Login button on my website, once I click Login th…
In other words, can I do the following:
OAuth login from local PC
After successful login, the redirect url is that of the server with registered static IP on kite developer console
My server (the one with static ip) requests for access token
Al…
@sujith @Matti
If I have a linux VM which is console based and does not have UI, then how can I login using OAuth on that VM?
Is there a way wherein I can log-in from my local PC & have my strategy run on my linux box hosted in a cloud?
Usin…
@sujith @Matti
If I have a linux VM which is console based and does not have UI, then how can I login using OAuth on that VM?
Is there a way wherein I can log-in from my local PC & have my strategy run on my linux box hosted in a cloud?
@sujith I understand that this is not something that only Zerodha is doing. However, this static IP mandate is going to add too much of unnecessary overhead. At the same time, traders will be carrying the risk of losing the internet. Even if we can …
@Matti The problem with taking static IP from local ISPs is that if there is an internet outage, we cannot do much. Currently, if there is an internet outage; then I can immediately switch to different ISP (Example, I switch from BSNL to AirTel). Sw…
@sujith @rakeshr
Patience are running out now... Even after multiple questions...still no concrete answer on what are the limits applicable per IP.
Just like other vendors, we also have no choice now to ask our clients to start shifting to other …
@sujith @rakeshr
https://kite.trade/docs/connect/v3/exceptions/#api-rate-limit
Are these limits given on above link per user or per IP?
Could you please shed some light on what are limitations per IP?
@rakeshr
As per the throttling notes, I see following line.
We have introduced a small throttling period to reduce the bad requests load effect.
What it tells us is that when there are bad requests, then it will cause throttling. But we need mor…
@rakeshr
I have given you list of IP addresses.
I still wonder what changes were made recently. Could you please shed some light on that?
Because the API limits were always present, we never got "Too many requests" error. And these days even af…
@sujith @AbhyudayaCodes25
1. Order cannot be modified as it is being processed. Try later.
2. MARKET orders are blocked for stock options due to illiquidity
Two more examples of Bad Request for which you cannot have validation upfront.
Error 1 -…
@sujith
"Some" of the causes of bad requests:
1. 400-Buy orders are blocked for this strike price due to [open interest (OI)]
2. Order price outside circuit limits
3. Non-amo order placed outside market hours
For reasons like point 2 & 3, ob…
@sujith
I understand the measures taken to reduce load caused by bad requests. I have a a few questions:
1. Is the IP limit still active? (250 requests in 10seconds from single IP). I am assuming this limit is for valid requests.
2. How many bad …
That's very strange. For us, I am observing significant delay every day now....since this issue has been reported. Before that it worked absolutely fine.
My server is on Google cloud mumbai data center, so it is definitely not a network issue/lag f…
Thanks Rakesh,
Could you please confirm if you checked both tick time & system time. Because if ticks are delayed then there will be difference in tick time & system time/internet time.
Please note that this issue happens randomly. On some days or to be specific sometimes we observe it, other times we do not.
This one would be difficult to trace.
Guys,
Any update of this? This is still happening.
Please note additional points in reproducing this:
1. The connection must be open for some time for the delay to be observable
2. The connection must have a lot of symbols (Say around 1000) subscr…
This issue has popped up again. Please try to reproduce it today with the following steps:
Steps to reproduce the issue are:
1. The connection must be open for some time for the delay to be observable
2. The connection must have a lot of symbols (S…
Hello Sujith,
You can ignore that file, as it will most likely match with kite website. However as mentioned in my previous comment, this data was taken from my local test environment. I do not see any delay there.
The delay is observed on my produ…
Another important observation here.
I do not see any issue in my test environment. That socket has subscribed to just one symbol. But when I compare prices from my test environment kite client with my production environment kite client....I see qu…
I have attached sample data. Please check beginning and end. I was busy so could not monitor the difference visually.
This data is from test env & i dont see delays visually. Please see next comment.
Thanks Sujith,
There was or is definitely something abnormal today. I do understand it would be a difficult to investigate, but keep an eye if anyone else reports any issues that could be connected with the delay happening or happened today morning.
You wont see it immediately. Keep the client open for a while & then you will start seeing the delays.
As mentioned in my earlier comment, if I restart my client. The delay goes away for a few mins & then it comes back again.
Same thing is being observed by me as well. If I restart my client, then for some time the price matches. And after a few mins I can see it getting delayed.
Mode Full, comparing LTP with Zerodha kite app.
Comparing it with Zerodha kite website.
Difference is mostly evident in active contracts like banknifty sep future. I can see a difference of 10-15 rupees.
