It doesn't make any sense charging 2000 rupees in the name of "APIs" while nothing can be automated without hacks with the APIs. A simple auth flow now requires manual input. You guys should seriously consider the pricing of the APIs as with all the…
@sujith: This is not a timeout. Instead this is a 503 which means that the server was unavailable to process request. According to HTTP conventions, this error code is something that is temporary and has to be re-tried.
Adding hack in client to sup…
@kyaboltitu: I have raised such concerns multiple times with kite team that they need to be professional with the APIs, atleast because its a paid service that they are providing. The least they should do is notify clients of any API contract change…
@sujith : I might be wrong when i said the bug is in python kite connect.
My observation is that whenever I am subscribed to websockets with order updates, and there is a re connect, the order updates stop coming. You can try reproducing it at your…
@sujith @vivek : this doesnt make any sense. If close price was the last tick you received (as you are saying), then this data would be correct. However, the current close price is some random data that stays as is for the complete day. Plesse fix …
@sujith Can you please check and respond on this ? Close data is still incorrectly being returned as 10806.5
The data is wrong even on kite web ui.
Update: On checking I found that nifty closed at 10806.6 , so close data seems to be correct.
I think we should lodge a complaint in consumer court if they dont start refunding charged amount for days like these. They are for sure taking clients for granted. 45 mins and no response from any support executive.
@sujith what was the issue here.? Did it impact only equities or derivatives as well ?
If there is a ticker issue , you should be broadcasting a notification to all API users because the strategies heavily rely on LTPs. If there was an issue, p…
Can you please update on the status of this problem - https://kite.trade/forum/discussion/3404/logging-out-of-kite-trade-webapp-after-logging-in-the-api#latest
I hope you have not migrated kite to kite3 without fixing it.
@sujith Thanks for the workaround.
I have a question though. Do you mean I will not have this issue if I move to kite connect 3 and use kite3 ?
Also, please update this thread once a solution for this is in place and deployed.
@sujith but you are missing the point here. Why was 403 even thrown in the first place.
I had successfully authenticated the API, then I authenticated using web. After this, token that was saved from API auth started throwing 403.
On 403, logging…
@sujith I directly opened https://kite3.zerodha.com/positions and landed on the login page.
From the mobile app, I opened the app - It went to the last screen I was on (market-watch). Then it went to the login page.
This is not intermittent. Calls start failing consistently .
To Reproduce, follow the steps:
1. Login to client connect API and generate access token using request token.
2. Open python command line (or any other supported language comman…
@sujith BTW I have tried getting the current token and using the same to get historical data.
Does not work
KOTAKBANK17OCT780PE - has instrument token 12995330
@sujith I went through the thread.
It makes sense if data from two different brokerages do not match.
However, it makes no sense that on kite web I see some other volume data while from the kite APIs I get a totally different value. It makes vali…
@sujith - I know that. I am calculating volume from day's data.
What about the historical API ? Can you check - HINDPETRO, 1 minute bars, date 2017-09-27 14:28:00 from historical API and what is shows in kite web volume chart. They do not match.