It is not a rate limit issue. You would see 429 or too many requests error for rate limits.
Does it reconnect after you see this error since you have set reconnection true on kiteconnectjs or you have to stop script and re-run?
Can you try on two di…
It could be related to the network issue. It could be because of some exception in another thread or in the script and it results in this the error.
You may use the inbuilt reconnect feature in the Kite Connect library. The heartbeat listening and r…
Kite Connect doesn't offer option chain out of the box. You will have to create option chain at your end. You may refer to the library which might help you in that.
Anyways, you may write to business team on kiteconnect(at)zerodha.com and check if they can give you refund or credits, since it happened by mistake at your end.
@jitesharora,
The way developers console works is you add credits and use that to create or renew Kite Connect subscription. You would have already used the credits for creating the app. If you delete an app then it won't affect the credits that was…
You may send order modification request with new order type. You may refer to the pykiteconnect documentation here.
You may also check out the API documentation here.
Kite Connect is purely an execution platform. We provide historical data for backtesting purposes only. You may write code at your end for indicator calculations.
Unfortunately that is not how RMS works. It is always calculated against the portfolio or account level.
If you want to know the required margins for each order then you may use margin calculation API.
@DaneshBansal,
We apologize for the inconvenience. @Sravanthi_bh was thinking in the Kite Connect perspective. This is a client level restriction outside of Kite Connect. We just got to know from the concerned team after an elaborate back and forth …
There is no limit on number of items that can be added while requesting for margins but you need to make sure you don't hit the global request size limit of 100kb.
Each connection allows to subscribe for up to 3000 instruments concurrently. Hence concurrently you can subscribe for up to 75000 instruments. It is more than enough for any kind of usage.
In some cases, it helps backend to decide if the GTT is a target or stoploss and in some other cases when there is a high volatility, the price that is displayed on the frontend and the price when request reaches the backend might be different and t…
The historical tradebook is not a part of Kite Connect APIs. It is a part of the Kite Connect APIs. You may find it on console, our backoffice platform.
Kite Connect is purely an execution platform. We provide historical data to our clients for personal use and only for backtesting. The only way to check if it is our client or not is by doing an authentication which is done by sending the api_key an…
The instruments API doesn't have authentication for now because of the legacy reasons but other API calls are behind the authentication.
You need to make sure you don't call the generate_session for every run. You can refer to this thread.
You seem to have added credits to the developers account but created Kite personal app. You will need to create a Kite Connect app on the developers console.
@AEonAX,
Kite Connect is purely an execution platform wherein we provide historical data for our users to do backtesting.
It is provided only for personal use as per the regulations. You may have to contact any exchange registered data vendor for hi…
It seems like you have deleted this app. You can use the new app's api_key.
PS: Make sure you don't share the app and client specific tokens on public threads. You may private message if you have to share these tokens.
@Shubham0406,
yes, earlier it was 2000 for base Kite Connect subscription and an add-on subscription fee of 2000 for historical data API. Now it is free with base Kite Connect subscription.
You might have given localhost as the redirect url. It doesn't matter if redirect url loads or not you can just copy request token from the url and use it to generate the access token.
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.
