For multi-user access,you can check with the compliance team . Write to kiteconnect(at)zerodha.com. Make sure you include complete information about your product.
The simplest way is to fetch quotes at 2 points of the day.
First, just after the normal market closes at 3:30 ,but before 3:40,i.e the post-market session opening time.
Let's say the volume in the quote is x.
Second,fetch quote again…
You are passing invalid value for variety. Variety should be in lower case ,not upper case.
Please read the documentation properly:
https://kite.trade/docs/connect/v3/orders/#glossary-of-constants
No.
As told above,you need to calculate post market volume before EOD because post market data is removed at EOD.
The difference between the day's volume and sum of volumes of all 5 minute candles is beacuse Zerodha doesn't get all the ti…
This isn't possible. You can't get today's data if you use datetime.date.today(). To get today's data,you have to use datetime.datetime.today().
And as told above,you do get the latest live candle if you fetch data until current time.
As I said,the stoploss field was for BO which has been discontinued. If you place a buy order with price at 0.1, it will be placed as a separate buy order.
To place a stoploss order,you have to place a separate stoploss order with order_type a…
Depends on the 'to' parameter you input.
If you fetch data data until current time,you will get the current running candle as well.
In that case,you have to look at the 2nd last row for the last completed candle.
Please read the documentation properly.
https://kite.trade/docs/connect/v3/orders/#regular-order-parameters
' price' parameter is the price to execute LIMIT orders at.
So,your buy order will be executed as a separate order and not a …
This forum is purely dedicated to KiteConnect APIs. Please write to support for queries not related to KiteConnect from next time.
https://support.zerodha.com/
For now,there is no such feature in Zerodha.
You need to have the full requir…
It's not possible using KiteConnect API data.
As told by Sujith Sir in the above mentioned thread,you need tick by tick data to calculate number of trades.
There is no other way ,you have to filter from the instruments file.
And to reduce the time,the best way is to download the instruments file as csv directly rather than calling instruments method,and use that . It will take less than half a sec…
Any error can cause this. Like, write 1/0 inside on_ticks and the TCP error will occur.
If you are sure that no error happened in your program,then it might be happening due to really heavy computation.
You can try queue method as describe…
Query about TCP error has already been answered in one of your previous threads.
https://kite.trade/forum/discussion/comment/39433/#Comment_39433
About the websocket not connecting after this error without throwing error,t's because you ar…
@tahseen Sir,
The current login flow requires 2FA TOTP instead of pin.
Without this,the orders will not go through.
You can read this announcement to know more:
https://kite.trade/forum/discussion/10391/mandatory-totp-for-all-kite-c…
https://kite.trade/forum/discussion/11558/excess-payment-debited#latest
It seems you are the same person who posted the above query.
The words match exactly.
Please, don't spam by making new accounts.
You might be blocking the main ticker thread receiving ticks resulting in delay.
You have to offload all the computation to another thread asynchronously without blocking the main thread.
Also, it's not necessary that you will get a tick eve…
You have to use historical data API to get candles for a specific timeframe.
https://kite.trade/docs/connect/v3/historical/
Or you can use websocket and build candles at your end.
https://kite.trade/forum/discussion/2604/convert-tick…
All the official clients are updated as and when new features have to be added or any bugs are encountered.
All official clients are in parity with each other.
I found out the issue.
You are using an extra backslash in the url.
Refer this thread:
https://kite.trade/forum/discussion/comment/36016/#Comment_36016
At first ,I thought this is the error,but I couldn't understand how even the…
You have to fetch with exchange as 'NSE'. And sort with segment as 'INDICES',to get all the indices data.
Also, fetching NFO instruments returns all futures and options instruments,not just options.
The continuous polling of quotes is delaying ticks,and making some ticks miss too.
So,your observation that market quotes are faster than websocket ticks is just an illusion.
Threaded ticker example is given here:
https://kite.trade/forum/discussion/comment/25535/#Comment_25535
And as explained multiple times, it's impossible for market quotes to return a tick before websocket as quote API just fetches the latest …
We don't provide one to one support on a call. You can ask your queries on this forum.
1. You can sign up and make a KiteConnect app on the developer console.
https://developers.kite.trade/signup
Here is the KiteConnect API documentat…
We don't provide programming support on this forum.
You have to use websocket data and build candles at your end.
Refer this thread:
https://kite.trade/forum/discussion/2604/convert-ticks-to-candle
Yes,the KiteConnect python client handles auto reconnection for you.
But ,it can't happen if you use 'stop' method as mentioned here:
https://github.com/zerodha/pykiteconnect#websocket-usage
https://github.com/zerodha/pykiteconnect/blob…
Also,you can use limit or stoploss orders instead of market orders to avoid slippage.
https://support.zerodha.com/category/trading-and-markets/product-and-order-types/order/articles/what-are-limit-and-market-orders
Callback to on_ticks is needed after redefining on_ticks.
Because redefining on_ticks only redefines the on_ticks function in your program,but the on_ticks attribute of the KiteTicker object is still unchanged.
Callbacks are a must for …
Websocket is recommended to stream realtime data.
https://kite.trade/docs/connect/v3/websocket/
You can refer sample websocket code here:
https://github.com/zerodha/pykiteconnect#websocket-usage
No, the threaded ticker does help.
The connection disrupts very easily without using threaded ticker.
The threaded ticker gives some time to do computations without closing the websocket connection.
But when doing really heavy computa…
The code looks fine at the first glance.
Try to run just a simple websocket code,like shown here and check :
https://github.com/zerodha/pykiteconnect#websocket-usage
If there is any problem when running sample code,you might ask here.
…
The instrument token solution was for the websocket error of parsing tokens.
Your issue has been discussed in the first part of the thread. You can use the default python setup instead of anaconda environment as told in that thread.
@rakeshr Sir,
In the morning,the exposure was actually showing 0 for the basket shown by @shbhnkr .
Also,the exposure was showing 0 for just the call short position(Tatasteel 1100CE).
I had made a test basket on Kite too consisting …
Expired options data is not available.
Only expired future contracts data is available as daily candles.
Read more about continuous historical data API here:
https://kite.trade/docs/connect/v3/historical/#continuous-data
Historical data API is an add-on over the base KiteConnect subscription.
So,you need an active KiteConnect subscription to use historical data API.
Because you deleted your app,you have to make a new app.
For multi-user access,you can check with the compliance team . Write to kiteconnect(at)zerodha.com. Make sure you include complete information about your product.
I told you above 2 times, it's not a bug.
It's the design, otherwise the code to parse the expiry wouldn't be there,as expiry by default is a string.
Read my above comment properly.
Yes, the API documentation specifies it as a string.
Actually,when you call the instruments API,it returns a csv file. So,'expiry' by default is a string.
As told above,the python client converts it into datetime.date object for ease. Refe…
This isn't an issue.
KiteConnect python client converts the string into a datetime.date object for ease.
If you want it in string format,you can convert the datetime.date object back to string.
You can use it any time.
However, historical data is provided only for backtesting purposes.
It's recommended to use websocket for streaming realtime data.
This can only happen if you set mode outside on_connect callback. As the default websocket mode is 'quote'.
So, after reconnection,the first tick will be sent in 'quote' mode and the subsequent ticks will be sent as per your set mode.
How…
You can refer this thread:
https://kite.trade/forum/discussion/11551/nifty-future-instrument-token
Also,you can combine another filter,with name as 'NIFTY'/'BANKNIFTY'(or any other underlying) ,with the segment filter('NFO-FUT') to get all th…
You should have read the warning message properly when you were trying to delete your app.
It's clearly mentioned in the warning when deleting an app on developer console that there will be no refund of credits which were used,upon deletion.
…
You are not getting any error.
Status code 200 means your request was successful.
Refer the sample code on GitHub here:
https://github.com/zerodha/pykiteconnect#api-usage
You don't need to generate request_token and then access_toke…
As stated in the error message,your checksum is invalid. Your api_key and api_secret are literally 'key' and 'secret'. Try with the actual api_key and api_secret provided when making an app on the developer console.
It will work properly.
Why do you never read the provided documentation?? Information about different modes is given.
Coming back to your original query,have you ever read about open interest?? Read about open interest here and you will know why oi is showing 0 for s…
For which instruments are you fetching quotes?
And make sure you are fetching full market quotes ,as other modes don't retrieve oi data.
https://kite.trade/docs/connect/v3/market-quotes/#retrieving-full-market-quotes
As told above,we don't provide programming support on this forum. This forum is purely dedicated to KiteConnect APIs.
Tradingsymbol format has been mentioned above.
You can use the same or sort with segment as 'NFO-FUT' ,incase you don't kno…
All the instruments available on Kite are available in instruments list.
The correct format for tradingsymbol of future instruments is:
Underlying+YY+1st 3 letters of the Month+FUT.
Like- NIFTY22JUNFUT.
We don't provide programming support on this forum.
You can sort with the tradingsymbol or any of the columns of the instruments list to find data for your desired instruments.
https://kite.trade/docs/connect/v3/market-quotes/#instruments
You can read the KiteConnect API documentation and python client documentation here:
https://kite.trade/docs/connect/v3/
https://github.com/zerodha/pykiteconnect
The candles received through historical data API and on the Kite charts can't differ,as they both use the same database.
Refer these threads:
https://kite.trade/forum/discussion/7798/historical-data-candles-inaccurate-for-small-periods
…
By default,an API_key is restricted to a single Zerodha user_id.
For multi-user access,you can check with the compliance team . Write to kiteconnect(at)zerodha.com. Make sure you include complete information about your product.
