Please refrain from posting app and client-specific data on the public threads.
The 64.0000m is a .NET notation, api doesn't understand this.
Another thing is Zerodha doesn't allow market orders for options. You need to place a limit order with the…
It is a library by @botany02 and @HowUTrade team. Maybe they can help you out.
There are a lot of similar threads which you may refer as well using the search feature on the top.
Can you private message your client id and give us example order of the same day? The order history is not preserved at our end after the end of the day.
There is only one base subscription plan with Kite Connect which includes everything. Only add-on is historical data which requires an extra effort from us to maintain.
@Rudrakanth,
I am afraid we can't do that as of now. We recommend generating candles for live strategies at your end using the live market data provided via websockets. You can get started here.
You seem to be sending an invalid variety. IOC is a validity param which indicates immediate or cancel order.
You can check out documentation for correct variety types.
It seems like you haven't subscribed for Historical data API. You have just added 2000 credits to your account. You need to go to app details page and subscribe for the historical data.
Though you can use historical data API to fetch this for testing purposes. We don't recommend using this in the live strategies.
For live strategies, you can generate candles at your end using the live market data provided via websockets.
You may re…
You need an add-on subscription to use historical data API apart from the base historical data subscription.
We don't have a sandbox environment yet.
You can get all the details via API except the historical data after you subscribe for Kite Conne…
A Kite Connect app is only provided for individual users by default. You need to get muli-user access if you are catering it for masses. You can write to compliance here kiteconnect(at)zerodha.com
You can check here to know more about the from and to date params. The finest resolution is minute, even if you send the seconds value, you might receive the latest candle only.
The max limit is 3000 instruments per websocket. The missing ticks are probably of network conditions, unavailability of the process which is receiving ticks. I would suggest using multiple threads and let the main thread always ready to listen to t…
Thank you for pointing out. We have updated documentation and we missed an update here.
You can check out the documentation for instrument dump here https://kite.trade/docs/connect/v3/market-quotes/#instruments
We don't recommend using the historical data API for live strategies. We provide historical data only for backtesting purposes. As mentioned by @rakeshr, I would recommend you to generate candles at your end.
The exchange sends these values in Unix timestamp. We convert it to milliseconds and to a Date object.
Ideally, it should be converted to IST if you are out of India. If not, then default system time zone is considered which will be IST.
The Kite chart shows intraday data for live instruments only and not for expired instruments.
For expired futures instruments, we only provide day candles.
A refresh token is only for the platforms which are catered for masses and not for individual traders. One needs to log in at least once in a day as per the exchange regulations. Hence we don't recommend automating login.
Access tokens are flushed …
The basket orders feature is only for Kite publisher. The API clients still have to loop and send individual orders. This is to ensure that the client system could know the status of each order placement as our system also places individual order at…
Hi @RP3436,
The P&L calculation for positions is straight forward, you don't need to poll positions to check that.
You can refer that this for formula.
You may use websockets postbacks for order updates.
@chethan_kumar,
You seem to be blocking the main thread. The idea is to keep the websocket listener in one thread whose task is only receiving the data and nothing else. Use some slave threads to do your operations. This is a very common mistake eve…
This is a historical data API and Kite charts use the same API to populate data.
One needs a live Kite Connect and historical data subscription to fetch the data. If you are not aware of the programming then I would suggest hiring one of the freelan…
You can download this report from our backoffice known as console.
As of now, Kite Connect only includes APIs for trading platform. We may provide this when we include the backoffice APIs.
Can you let us know when this happened?
Is this consistent or intermittent? Please do paste request and response samples here. We will check and get back to you.
I don't think exchange send milliseconds level data. Even on the python library, you will see only seconds level data. The milliseconds are added at the client library by multiplying 1000 for parsing.
Kite Connect is only for retail traders and not for HFT. For HFT, you might need a colocation server setup at the exchange.
We do keep changing the values. The ideology we follow is to cache the data and use it rather than assigning variables direc…
@krtrader,
It is already pinned from a very long time. It comes under FAQs.
The point is nobody looks at pinned posts. People want readymade stuff and still keep asking for the same.
The order time gets updated every time there is an update to the order by the system or from the user.
Can you check the order history and let me know what is the exact issue?
PS: It is possible that there is a delay because at the opening we fire …
You can modify the price of a cover order entry type limit if it is not executed.
If the price is not changed after the modification request then you may see the reason for not modifying in the status message field of the order response.
The above-pointed thread has the updated rate limits. Apart from those, there is a maximum limit of 200 order placements per minute.
Apart from API limits, there is also an account level order limit set by the Zerodha RMS and that is 2000 MIS orders…
@cheko,
You are blocking the thread. The magnitude of the load depends on the number of instruments you are dealing with. If you have more writes to do then your program becomes unavailable for receiving next ticks.
@cheko,
This repository might be helpful for you.
The idea here is the Tick receiving module will be a producer and the post-processing module will be a consumer.
The producer keeps pushing messages to bus and consumer keeps reading one by one.
