You can run javakiteconnect with debug flag and paste the complete error json with status code here.
Also paste the response and status code of the api that is successful also.
PS: Make sure to remove app or client specific tokens.
Kite Connect app is provided only for single user only. You will have to create another app if you want to use it with another account.
If you are developing a platform for mass then you can write to kiteconnect(at)zerodha.com for multi-user access…
This limit has been there for more than a year. We haven't made any changes. If you have exceeded the order modification limit then you need to cancel and place the order again.
Can you give us more details about it? Is this while modifying the order or placing the order.
The order count is considered even for the ones that got rejected by our mini RMS. If an order is rejected by our mini RMS then you will receive 400 error…
Once you place an order, it goes through various internal systems and then finally hit the exchange and then OMS updates the value and the change is propagated to all the connected systems. You can add a delay after placing order before fetching pos…
The refresh token is only provided for the apps that are made for mass and is approved by the compliance team. In the above case, it seems like compliance team didn't approve of providing refresh token permission.
@Anbalagan,
Kite Connect only exposes place order API. Kite Connect doesn't differentiate between entry, exit order, target or stoploss order. It has to be tagged or maintained at your end.
During non market hours, the API returns the cached value. It might be 0. You can try during market hours.
And make sure you are subscribing to live instruments and not the expired ones.
You can check out API documentation here.
All the params are for the day. It is average traded price of the day. The total buy quantity is the sum of all the buy orders quantity currently pending at the exchange.
You need to make sure the main thread is not blocked. If the connection disconnects then you will need a new access token to reconnect and for that you will need to go through login process.
@stalwalk,
Thank you for pointing out. The allowed length was 8 earlier. We increased it recently to 20.
We will update the javadoc in the next release.
Our system listen to every incoming tick and build a candle at the end of the minute. This happens for all the instruments present in the instruments master. As you know, DB writes are not guaranteed, if one of the write request slows down then it h…
The stoploss and target params are for the bracket order. It is not used anymore. We will update the documentation.
You will have to place a stoploss and target order or use OCO GTT, once the entry order gets executed.
Hi @Benthomas,
Zerodha support doesn't deal with compliance related stuff of Kite Connect APIs.
We are the developers here on the forum, we don't deal with compliance stuff either. You can email to kiteconect(at)zerodha.com or DM matti for the foll…
You will have to place an order by checking bid and ask probably. For immediate cancellation, you will still have to place an IOC order but with an additional check at your end.
Client library will just convert the binary data to user readable format.
The latency can't depend on the client library. The Kite Ticker just publishes data when there is a change and client library will parse the data.
@Sandeep_Prakash,
The order update events are async and are send by the OMS. We just relay them. The correct practice is to pull orderbook or order history when you receive an order update.
UPDATE is not a real status of the order, it is a place ho…
Issue is after expiry the exchange might re-use the same token for some other instrument. Hence it will mess up the whole instruments master.
And it will be very difficult to maintain and may require a lot of work to overcome this scenario and also …
@sunil354,
If you are not using them simultaneously then you may change redirect url and postback url and use it.
If you are using them simultaneously then you will need a new subscription.
Kite Connect is purely an execution platform, we don't provide solution or support for writing strategies. However you can check out few community libraries and useful resources here.
Stocks can be moved to BE, BZ, BL series (called trade to trade segment) by the exchange for any reason, after few days it is moved back to EQ segment by the exchange. We just follow whatever is being provided by the exchange.
There are various reas…
If it is not disconnected then next day, Websocket won't close existing connection.
You will continue to receive ticks even after access token is expired.
I think you should use Kite web or app first to understand the concept. Positions is a mark to market view of the account, it is not related to orderbook.
Orderbook contains the list of orders placed by the user and it shows the status of the order …
Tradebook is not directly related to orderbook, both are different data linked with an order id in the backend AFAIK. Hence pulling tradebook data for sending postback doesn't make sense for Kite Trade.
@mnkartik,
This is a field introduced for supporting new features we are going to introduce in future releases. For now, this is a map of arbitrary data.
@DevTrinkerr,
We are trying to reproduce this error but we couldn't. Is this a consistent issue or intermittent?
Does it happen at the opening or during the day also? Any hint to reproduce this consistently will be helpful.
We did try this out multiple times, but we couldn't reproduce this. We will ask the team to try and reproduce this again today.
If you come across a pattern or behavior to reproduce this, let us know.
The historical data API is provided for backtesting purpose only. You need to generate candles at your end for live market strategies.
The ideal way to use it is to dump all the data required at your end and use that as a source.
Quote and LTP APIs are limited to 1 request/second. You may either club the instrument tokens and send one request for all at once or use Websocket API.
You can refer to the API rate limits in the FAQs.
You can check Utilities section here.
For now, we don't have an API for that. In future, we may come up with a feasible solution.
Or an alternate solution is to place an order and check for now. If you don't see 400 error, then it is allowed.
It is not recommended to poll positions. You need to fetch it and cache it. It changes only when there is a partial fill of an order or when order executes.
A Kite Connect app is provided only for single user. It can't be used for multiple client ids?
If you want multi user access then you can email to compliance team on kiteconnect(at)zerodha.com and make sure to include the product details.
This is because of the cookie management policy change on the iFrames. Our team is investigating the alternatives for this. We haven't arrived at a concrete solution yet.
