You shouldn't block the thread that is receiving ticks. You need to offload all tasks like doing calculations or writing to DB to another thread.
You may refer to the pykiteconnect FAQs here.
The binary data is the live market data like ltp, OHLC, etc.
The non-binary data are the order updates, and other non live market data.
Have you checked the iceberg order?
@dheeraj,
Your subscription seems fine. Are you sure you are sending the authorization header properly? Can you enable debug logs of the Kite Connect library and paste the complete stack trace in a private message? We will check and get back to you.
You may check with the compliance team. A third party app is not allowed to show our data on their website.
You can write to kiteconnect(at)zerodha.com
Hi,
It seems like the concerned person handling this query is on an emergency leave. We will arrange a callback by next week. We apologize for the inconvenience.
Kite app authentication is provided only for the exchange approved partner apps. You may speak to the compliance team to know more about it. You may write to kiteconnect(at)zerodha.com
A success response for modify order request doesn't mean order is modified. It means the order modification request is success. Once the request reaches Kite Trade, it is passed on to our internal mini RMS, other OMS and OMS checks and exchange chec…
@hirak_vrid,
You may write an email to the compliance team with your product details and demo details. They will review case by case basis for multi-user access. You can reach out to them on kiteconnect(at)zerodha.com
We don't see any issue with your subscription. You need to generate a new access token as mentioned in the documentation and user that to fetch live market data.
What is the exchange value you are sending in the request? Is it same as the one that is mentioned in the instruments master for the corresponding instrument?
The first order will go through with the quantity specified that is 1200 and then the second order will be placed with the quantity of 2475-1200 (1275)
@yc_mhk,
NSE has changed the tick size for all the instruments traded on the exchange including cash and F&O segment.
The tick size is based on the last price(as of 28th march 2025) slab now. You can know more here.
The ideal solution is to use…
You may initialize Kite Connect object with debug log true as mentioned here.
We need request and response json to know what is happening.
PS: Make sure to remove app and client specific tokens.
quantity signifies how much you hold in the DEMAT account.
realised_quantity it is a legacy quantity field, don't use this.
used_quantity denotes the holdings units sold today. It will get reset to 0 the next day.
We have it on our todo list but unfortunately it is not a priority task since it has OMS vendor dependency. Kite Connect personal is free, users can place order after market or from an account that doesn't have balance and test out the APIs.
Hi @namratasonawane,
The order_id is required for some technical reasons in the backend, Hence we expect it to be in the body params even though, it is already passed in the url.
We don't or can't make up tradingsymbol, we create tradingsymbol based the instruments master published by the exchanges everyday. We suggest doing the same at your end as well instead of generating tradingsymbol at your end.
Kite Connect can't offer the FTP data services because of the regulatory reasons. You can contact any exchange registered data vendor for this feature.
Kite Connect API only contains trading APIs, it doesn't contain backoffice APIs. The trading platform will only contain order and trade related data for the day.
This is a webpage, I don't think you can use postman for that. You can know more from the API documentation. It is mandatory by the regulators that users have to manually login at least once a day. We don't recommend automating login.
@bhaskarsancheti,
Are you getting this after login or before that?
PS: Please create a new thread for the issues, it may help others who are looking for similar solution. Don't hijack existing threads.
@chpadma,
Are you sure you are using the right api_key and app_secret? Please create a new thread for the issues, it may help others who are looking for similar solution. Don't hijack existing threads.
The tradingsymbol is something that exchange decides and publishes. We have no control over it. The only way to keep our systems up and running is to maintain a static mapping at your end and use it. We also do the same as it is inevitable.
Have you added callTimeout for the interceptor? This looks like some issue with Okhttp library. You can google it and figure out.
It is not Kite Connect exception.
The historical data API is provided for backtesting purposes only. It is not feasible for live market strategies. We recommend generating candles at your end using the Websocket API.
You can get started here.
@kanika,
The instruments master is generated in the morning after BOD process, it will not contain live market data. You need to use Quote or Websocket API to fetch live market data.
We don't have the close price value from BHAV copy like NSE and BSE instruments. Hence whatever is the last price recorded on our platform is considered as close price. We have asked the concerned team to take a look at this.
We don't have a Kite Connect client library for RUST, if you are interested you can create and maintain one. We would be happy to feature your library.
