I would like to add, historical tradebook data is only available on our backoffice console.
Kite is a trading platform, it doesn't know the context of when purchase has happened.
@tapanjbhatt,
We would like to add that Kite Connect is not suitable for time based / low latency strategies. It is provided for retail use only. For these kind of strategies, it makes sense to co-locate your setup at the exchange premises.
Kite Connect isn't meant for high frequency / low latency applications but for retail use. If you need low latency data over internet, a dedicated data vendor is ideal.
A third party website can't show our market data. You can get data from an exchange registered data vendor.
Websocket data API provided on Kite Connect is provided only for personal use. Hence data can't be accessed on a website because of CORS.
@tapanjbhatt,
Only first leg order is placed initially, second order is triggered only after first leg is executed. Hence only one order_id is sent in response.
It might be working for legacy reasons now. This will be blocked without intimation, we suggest not open more than 3 websocket connections per api_key.
It is mandatory by the exchange that a user has to login everyday at least once.
Kite Connect only offers trading APIs currently. Tradebook is a part of backoffice.
The solution is to redirect users to console and make then download there and uploa…
@AAAAAAAAAA,
You may run with debug logs on and see the complete request and response flow with your print statements.
If you keep polling positions, CDN might think you are spamming so it might be blocking your request or it could be your network…
You are blocking the main thread that is receiving the ticks hence you are getting disconnected and reconnected.
We don't have any issue at our end. We use Kite Ticker on all our platforms and used by many Kite Connect users in production also.
You can refer to the FAQs here.
You might be doing some calculation or db dump which is blocking the main thread. One shouldn't block the main thread that is receiving ticks.
@madhumattangi,
You need to fetch instruments master file once and save it locally. If you keep polling then Cloudflare might block you thinking these are rogue requests.
When a stoploss order is placed and it is sitting in Trigger pending status, Kite Trade will not send a postback. It is only sent when the trigger is hit.
@sujanbabu67 Like @rakeshr mentioned there is no issue. We ran a script and found no discrepancy.
PS: If there was a stray tick in between then chart would show that as the high for that candle. We don't see it.
Can you let us know more about your setup?
This is not possible, randomly one tick having difference of one or two decimal places. Our charts also hasn't recorded this.
@Tamalk,
I'm afraid we can't add this to the session data or share this with entities that aren't Zerodha.
The solution is to show error dialog to user when order place request gets input exception.
@thepunisher,
We see the timeout error being logged at our end while sending postback. If you are doing some processing then i would suggest respond first with 200 and then continue doing processing.
It is because you haven't entered any postback url while creating the Kite Connect app.
You can go to developers console and go to app details page and set the postback url.
It might be sending 400 for second request whereas the first request has been served successfully. You may run with debug logs on and check. If this was an API issue, then all our production apps will fail and also the other 1000s of production Kite…
@Prem,
The range calculation is not a simple straightforward logic. There are many external factors and variables to be considered and it is done by the RMS.
we can't provide an API for this due to some technical issues. We may include an API for th…
@r2k1984,
If you see this error, then it means order is undergoing a modification or some kind of action happening on the order already.
If you had sent a cancel request, did you get 200 response with order_id or did you get any other response with …
Everything seems fine at our end. We haven't done any changes lately for login flow.
I tried with one of the test app as well and the login flow seems fine.
@Sidney,
We don't want users to keep polling positions API just to get P&L value. You can fetch positions when an order is placed or trade happens.
Calculate the realtime P&L using the Websocket API data and make your decision.
@Prem,
If this is particularly about checking the allowed banknifty or nifty strikes for trading then the easiest way is to place an order and check the range on the Input Exception's error message.
For others, you will have to use Consolidated lis…
@padalasubbu81,
The getOHLC is day's data. You will need historical data to get hourly candles.
You can know more about historical data API here.
Historical data API is for backtesting purpose only. We don't recommend using this for live strategies…
If there was one stray tick then it would have shown up on charts. since high would be 437.5 and even websocket would show high as this value for the day.
We don't charge for equity delivery. Hence there is no scope for earning commissions for stock recommendations.
We do have a Zerodha partner/sub-broker program but criteria is different. You can write to kiteconnect(at)zerodha.com and ask them to co…
One should never expose api secret to outside world, or never embed api secret on frontend apps.
Because of CORS, you won't be able to make a request from your frontend app.
You need to make request for generating access token from your backend app.
This could be connection pool issue, you can create a custom python connection pool and pass it to pykiteconnect
You can checkout documentation here.
Sample will be something like this,
from kiteconnect import KiteConnect
pool = requests.Session()
…
One can't place orders via Kite Connect if you don't have totp enabled. It is only possible to place orders via Kite web or app, if you have pin as the second factor authentication.
If you are scraping Kite web then it is against the terms of use.
Kite Connect is purely an execution platform. We don't provide one to one support for Kite Connect. This is a community driven forum. We are not support agents. We are all developers who work on our projects and take out some time to help out fellow…
It depends on exchange. NSE, NFO, CDS volume will get updated at around 4:30 PM to 06:00 PM but BSE will update at around 7 AM, next day morning.
Since trades happen (at LTP), volume will change.
It is very difficult to pin point the issue where this is happening. It can happen because of many reasons, it could be the client's connection with Kite trade, Kite trade's cloud connection to OMS data center or OMS overload, or OMS internal system…
