Our RMS blocks all the orders after market hours which will throw a Kite exception with a message as mentioned here. However, for the convenience of the Kite Connect users, we allow placing orders for ICICIBANK of NSE. You can use that for placing d…
The OHLC API gives you the day's data and not 5 minutes candle data.
If you are looking for candle data then you need to build candles at your end using live market data provided on Websocket API. You can get started here.
You will have to maintain a data structure of the holidays and use that to remove unwanted data.
You may also need to note that during muhurat trading the trading starts at 05:30 PM.
@haricoolharan,
We provide whatever data we have. If you are not satisfied then you can go ahead and get the data from any other exchange registered data vendor.
We don't guarantee any timeline for order processing. If you are working on a latency-based strategy then I would suggest not using Kite Connect.
You may go for a colo setup at the exchange which would cost upwards 18 lakhs/annum. You can write to …
Though only one session is allowed for an app, you can run multiple programs with the same access token.
You can listen to ticks, do calculations, and place orders.
I would suggest going through this thread. Make sure to read comments as well.
If you need data for every 5 minutes then I would suggest using quote API.
One can have only one active session at any point in time for a Kite Connect app.
@tfKamran,
We don't have any plans of providing an API for fetching the list of illiquid instruments. You can write a script and take it from the google sheet.
If you are sending a current month instrument token and the current month from and to date then you will receive the current month instrument data.
If you pass the current month instrument token and send last month's from and to date then you will r…
We provide continuous data for only futures instruments and in day interval only.
Can you elaborate, what is the meaning of assumptions regarding the roll dates?
The historical data is built using a different stream which is the same as the Websocket API. It is off because it might have missed ticks. We have asked the data team to take a look at this.
You can track progress on this thread itself.
@rajeesh31,
The Quote data comes from the exchange, so it will be the correct data always. We will ask the data team to take a look at the candle data.
It is not available yet. We will include it in future releases.
If you want it right now then I would suggest fork the kiteconnectjs and add oi param here.
The exchange allows institutions to settle or close positions after market hours. Hence you need to use the OI provided in the BHAV copy since it includes the post-settlement data for the day.
Though you receive 200 for delete request which means your request was successfully placed, the action was not carried out by the OMS because of the variety mismatch.
@Gopikrishnan,
It is on our list of things to do. I am afraid we can't give any timeline as of now. If you want to use it now then you can go ahead and fork the library, the client libraries are open source.
It is basically an exit order which uses the same cancel order API with parent order id.
If you don't send a parent order id then API will cancel it as a normal order and you will be in trouble end of the day since RMS looks at it as a hanging posit…
Yes, you are right. A success response for placing a cover order returns the order id of the parent order/first leg order.
In order to find the order id of the second leg order, one needs to fetch order book and search for the order with the parent …
A user can expect a tick when there is a change in at least one field that the user is subscribed to like be it open, high, low, close, total buy quantity, total sell quantity, or any of the quote mode fields.
You can check out FAQs to know more abo…
Can you private message the second leg order id and client id? We will check and get back to you.
You need to send co as the variety. I think .NET documentation is wrong if it says BO
Are you passing the order id and parent order id while canceling the order?
This is equivalent to exiting the order.
If you are then you need to open the Kite web and check if the second leg order is still pending.
If you placed order at market price then it would have already completed right?
If the parent order is already executed then you need to exit the order and not cancel the order.
You need to print the exception message and status code. You can check out the exception structure here.
You may also run it in debug mode to see what are the params being sent and what is the exact json response.
You can also check out this threa…
If you fetch orderbook and look for all the orders with parent order id then you will get all orders right?
It won't matter if there are four second leg orders or six second leg orders.
Ouch! thank you for pointing out. Here is the correct link https://kite.trade/docs/connect/v3/user/#login-flow
We will update the link in the next release.
